Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d3616aac3711fd73a226fb549c2f6277cbfd493ccd1e979f37d712bace23098

Tx prefix hash: 37dc0e5c038d29e3ded6cbb4d6878a8feb93645956f94461af86e299a38d34cf
Tx public key: 10d042d957aaeee9e16e5c7603311bc0474999e563bc19d7021c71b19f940b83
Timestamp: 1721319062 Timestamp [UCT]: 2024-07-18 16:11:02 Age [y:d:h:m:s]: 00:266:06:53:06
Block: 1068512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190214 RingCT/type: yes/0
Extra: 0110d042d957aaeee9e16e5c7603311bc0474999e563bc19d7021c71b19f940b830211000000030bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42781316f8a038c696a0a6043f091cc4a29b54834c8c309e1aa889ad47330366 0.600000000000 1539591 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": 1068522, "vin": [ { "gen": { "height": 1068512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42781316f8a038c696a0a6043f091cc4a29b54834c8c309e1aa889ad47330366" } } ], "extra": [ 1, 16, 208, 66, 217, 87, 170, 238, 233, 225, 110, 92, 118, 3, 49, 27, 192, 71, 73, 153, 229, 99, 188, 25, 215, 2, 28, 113, 177, 159, 148, 11, 131, 2, 17, 0, 0, 0, 3, 11, 186, 22, 215, 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