Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 60ef1eb0cb9ffb02bd2015d9dd970a18632c4da12f51c59209f5e2a81801effd

Tx prefix hash: 3a9f8a73e1208d7d313bcd5cff78035ae9bdd17bb542a1db971138025574524b
Tx public key: 6210a25f4377931c4c811662e7e732fd0e4195a86036fec030ae5e40b6535815
Timestamp: 1726116880 Timestamp [UCT]: 2024-09-12 04:54:40 Age [y:d:h:m:s]: 00:163:16:01:12
Block: 1108266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116770 RingCT/type: yes/0
Extra: 016210a25f4377931c4c811662e7e732fd0e4195a86036fec030ae5e40b6535815021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60ff2c5d0c6f15c93fece719fc12af807c78884d4a081d7f3a63e0e1239c2d66 0.600000000000 1586101 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1108276, "vin": [ { "gen": { "height": 1108266 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60ff2c5d0c6f15c93fece719fc12af807c78884d4a081d7f3a63e0e1239c2d66" } } ], "extra": [ 1, 98, 16, 162, 95, 67, 119, 147, 28, 76, 129, 22, 98, 231, 231, 50, 253, 14, 65, 149, 168, 96, 54, 254, 192, 48, 174, 94, 64, 182, 83, 88, 21, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8