Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7a5f8084d34b73ece644ee98f03ad749e3bbaea3cf9b7009d10c1a2a1f002d3

Tx prefix hash: 50098d2df9c97196745d38cbfea59740c6e508d1f465e26136571afcf7e2cacf
Tx public key: f629d6c3d3f90740a6ab1ab20af2e8ee5689f6e24528936ee4f662af6511d58a
Timestamp: 1726590996 Timestamp [UCT]: 2024-09-17 16:36:36 Age [y:d:h:m:s]: 00:196:21:55:49
Block: 1112196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140565 RingCT/type: yes/0
Extra: 01f629d6c3d3f90740a6ab1ab20af2e8ee5689f6e24528936ee4f662af6511d58a02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72233bf501d25d24c28dbd54ca86b5a2cd026d8f4cb6016073865651f13a1ab0 0.600000000000 1591431 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": 1112206, "vin": [ { "gen": { "height": 1112196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72233bf501d25d24c28dbd54ca86b5a2cd026d8f4cb6016073865651f13a1ab0" } } ], "extra": [ 1, 246, 41, 214, 195, 211, 249, 7, 64, 166, 171, 26, 178, 10, 242, 232, 238, 86, 137, 246, 226, 69, 40, 147, 110, 228, 246, 98, 175, 101, 17, 213, 138, 2, 17, 0, 0, 0, 4, 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