Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b36205a0f6e13fba312f9f873f793e25cb05b2f568f42ad77ca2e361d6f31dc5

Tx prefix hash: 14402fb31c7ac168c52138de55cf7045d2b868aeb5c5014914f7ff13b649f60f
Tx public key: bc5a48c76d6981d5d013f4eaa60dfe9d7413c6fcb371a29dc6e9dace8c4dfd12
Timestamp: 1728240692 Timestamp [UCT]: 2024-10-06 18:51:32 Age [y:d:h:m:s]: 00:165:04:07:17
Block: 1125870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117863 RingCT/type: yes/0
Extra: 01bc5a48c76d6981d5d013f4eaa60dfe9d7413c6fcb371a29dc6e9dace8c4dfd1202110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5184492c895dd8a7b0ac964b50ede136c1eeae7b78f6ad779dfa1884f7a20a19 0.600000000000 1608641 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": 1125880, "vin": [ { "gen": { "height": 1125870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5184492c895dd8a7b0ac964b50ede136c1eeae7b78f6ad779dfa1884f7a20a19" } } ], "extra": [ 1, 188, 90, 72, 199, 109, 105, 129, 213, 208, 19, 244, 234, 166, 13, 254, 157, 116, 19, 198, 252, 179, 113, 162, 157, 198, 233, 218, 206, 140, 77, 253, 18, 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