Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 050844adcb49725394acf92b8f01a808cfe3b433d4c8db43ec744bb4e00452ef

Tx prefix hash: 123bdd998de81cb301cf610de70e0ac9670a47b89af1d7745443e922dbc5ebed
Tx public key: aa2296cc5bd6624cdae4c97e7b28fdf951a28ddad3ba9a1acdbc7ea6b7a15aaf
Timestamp: 1717626348 Timestamp [UCT]: 2024-06-05 22:25:48 Age [y:d:h:m:s]: 00:233:01:19:29
Block: 1037874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166741 RingCT/type: yes/0
Extra: 01aa2296cc5bd6624cdae4c97e7b28fdf951a28ddad3ba9a1acdbc7ea6b7a15aaf021100000003d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34d2615d39475e99f428e9725bab56b6597d7453196abe3099b4d7d82e910d63 0.600000000000 1506431 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": 1037884, "vin": [ { "gen": { "height": 1037874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34d2615d39475e99f428e9725bab56b6597d7453196abe3099b4d7d82e910d63" } } ], "extra": [ 1, 170, 34, 150, 204, 91, 214, 98, 76, 218, 228, 201, 126, 123, 40, 253, 249, 81, 162, 141, 218, 211, 186, 154, 26, 205, 188, 126, 166, 183, 161, 90, 175, 2, 17, 0, 0, 0, 3, 215, 73, 245, 17, 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