Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2bb7d272f1e45559e9bfe5fcbcfb107608db83ff06348f9ab26b33bf822dfa7

Tx prefix hash: e4f5b0aeb9eb45f9fb945d07732faa636b220093f5831e3f96bb5900801a16c7
Tx public key: f05cb4e8706ed10ef6feeb44e952e24360ba6d6a89d2fb5608c57005c610b825
Timestamp: 1728794462 Timestamp [UCT]: 2024-10-13 04:41:02 Age [y:d:h:m:s]: 00:233:11:54:53
Block: 1130472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166707 RingCT/type: yes/0
Extra: 01f05cb4e8706ed10ef6feeb44e952e24360ba6d6a89d2fb5608c57005c610b82502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7236b24db25fdc8f70a675c5b74486441ec68a14bac0b338ccb351959077a8d 0.600000000000 1613349 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": 1130482, "vin": [ { "gen": { "height": 1130472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7236b24db25fdc8f70a675c5b74486441ec68a14bac0b338ccb351959077a8d" } } ], "extra": [ 1, 240, 92, 180, 232, 112, 110, 209, 14, 246, 254, 235, 68, 233, 82, 226, 67, 96, 186, 109, 106, 137, 210, 251, 86, 8, 197, 112, 5, 198, 16, 184, 37, 2, 17, 0, 0, 0, 5, 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