Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 824c10161c1980e05649047b6e7948bed7e78a83676fea89aa7bbc02616d5178

Tx prefix hash: 55262bc8ed834f6dc1ad92088714e25c509d4e91ecd710ae2aa5dc14012ebeaa
Tx public key: b095e76c50f02cc36acd8f1d34c0bee702ce5df6a0fb0ec115eca630ac410053
Timestamp: 1727516183 Timestamp [UCT]: 2024-09-28 09:36:23 Age [y:d:h:m:s]: 00:218:15:28:56
Block: 1119874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156075 RingCT/type: yes/0
Extra: 01b095e76c50f02cc36acd8f1d34c0bee702ce5df6a0fb0ec115eca630ac41005302110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46cc11d184a08eb8e5ec82f8cf0c09673b44bf41a366f5a9de116f76dbdb08cc 0.600000000000 1601589 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": 1119884, "vin": [ { "gen": { "height": 1119874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46cc11d184a08eb8e5ec82f8cf0c09673b44bf41a366f5a9de116f76dbdb08cc" } } ], "extra": [ 1, 176, 149, 231, 108, 80, 240, 44, 195, 106, 205, 143, 29, 52, 192, 190, 231, 2, 206, 93, 246, 160, 251, 14, 193, 21, 236, 166, 48, 172, 65, 0, 83, 2, 17, 0, 0, 0, 8, 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