Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2222b56246386c6750bd5d8ff4b250c61de06649c94010a7508f95f3e1f771a9

Tx prefix hash: 78fbb5c14dbba2f0b9c22be9021d053b0a132b15265d8d14c54e2a00f268964e
Tx public key: 484d2983d1a887ff90f2de494d9df45776f2fcbba493e36f8d03975bb17147b8
Timestamp: 1720728889 Timestamp [UCT]: 2024-07-11 20:14:49 Age [y:d:h:m:s]: 00:339:22:42:57
Block: 1063608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242817 RingCT/type: yes/0
Extra: 01484d2983d1a887ff90f2de494d9df45776f2fcbba493e36f8d03975bb17147b802110000001f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 015ae93fe12ba5c8aa02a4d0eb7ac0985776157916dfa0b17639e1b2fbeff1a4 0.600000000000 1534125 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": 1063618, "vin": [ { "gen": { "height": 1063608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "015ae93fe12ba5c8aa02a4d0eb7ac0985776157916dfa0b17639e1b2fbeff1a4" } } ], "extra": [ 1, 72, 77, 41, 131, 209, 168, 135, 255, 144, 242, 222, 73, 77, 157, 244, 87, 118, 242, 252, 187, 164, 147, 227, 111, 141, 3, 151, 91, 177, 113, 71, 184, 2, 17, 0, 0, 0, 31, 145, 225, 60, 4, 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