Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c472f7d47b110f237203f2da9d84791b9159c27d6a3233c36423817ce38e4ada

Tx prefix hash: 50dc89f7bbc901b379d9a3a0f6c5290a24add160fc946ac934207a2301b76c69
Tx public key: 71d0b0342de868d0f3f63d88a716f56529f9186b9e515a2bd6a2c7017948b5a1
Timestamp: 1731960520 Timestamp [UCT]: 2024-11-18 20:08:40 Age [y:d:h:m:s]: 00:124:10:46:36
Block: 1156611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88766 RingCT/type: yes/0
Extra: 0171d0b0342de868d0f3f63d88a716f56529f9186b9e515a2bd6a2c7017948b5a1021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6048594cd2b401cce8c46219223d2d31414103481d628a600675375f062552f 0.600000000000 1642234 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": 1156621, "vin": [ { "gen": { "height": 1156611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6048594cd2b401cce8c46219223d2d31414103481d628a600675375f062552f" } } ], "extra": [ 1, 113, 208, 176, 52, 45, 232, 104, 208, 243, 246, 61, 136, 167, 22, 245, 101, 41, 249, 24, 107, 158, 81, 90, 43, 214, 162, 199, 1, 121, 72, 181, 161, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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