Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 009d6cc7e0ae27f18a8bf35b9cf0abc4cbf1ab7c78b891971a18658962fe6150

Tx prefix hash: a1c9cc1a7e781cb70eecfead3c4baf9e848d4267754e30bd661ae1b2c3543d07
Tx public key: e0c5313fbd47658a0a89c7a8371de4aeb96aca3dd1e6704a1d55942958591a79
Timestamp: 1728229942 Timestamp [UCT]: 2024-10-06 15:52:22 Age [y:d:h:m:s]: 00:177:17:02:12
Block: 1125780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126800 RingCT/type: yes/0
Extra: 01e0c5313fbd47658a0a89c7a8371de4aeb96aca3dd1e6704a1d55942958591a7902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3adccbedeb281d6ad4819639773dc2a45cc8e631ccd93f71634b83f397e72a3c 0.600000000000 1608531 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": 1125790, "vin": [ { "gen": { "height": 1125780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3adccbedeb281d6ad4819639773dc2a45cc8e631ccd93f71634b83f397e72a3c" } } ], "extra": [ 1, 224, 197, 49, 63, 189, 71, 101, 138, 10, 137, 199, 168, 55, 29, 228, 174, 185, 106, 202, 61, 209, 230, 112, 74, 29, 85, 148, 41, 88, 89, 26, 121, 2, 17, 0, 0, 0, 3, 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