Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d656b21a9cdde387d3de4af6dcf37085a80d0e7f260e76c032cb6d63cce51d9

Tx prefix hash: a5eee55e207112990213fa1d0d1cd14e2f7431fec7687aebd9a5d85dbc7fbfc3
Tx public key: 0c167e4290cb14a96d48a21d0a4a38c8ce2e6649b4cb45275cd70b2f930b116e
Timestamp: 1712196913 Timestamp [UCT]: 2024-04-04 02:15:13 Age [y:d:h:m:s]: 01:221:03:45:55
Block: 992830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416767 RingCT/type: yes/0
Extra: 010c167e4290cb14a96d48a21d0a4a38c8ce2e6649b4cb45275cd70b2f930b116e0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34422b71baab438629d90dc524a7aaefdb302fa259bb0d075ad252b1c263b664 0.600000000000 1453204 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": 992840, "vin": [ { "gen": { "height": 992830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34422b71baab438629d90dc524a7aaefdb302fa259bb0d075ad252b1c263b664" } } ], "extra": [ 1, 12, 22, 126, 66, 144, 203, 20, 169, 109, 72, 162, 29, 10, 74, 56, 200, 206, 46, 102, 73, 180, 203, 69, 39, 92, 215, 11, 47, 147, 11, 17, 110, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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