Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01a831af3cd242d14531afad6ba59b375add6b6b9e44012a6fa1e3db4f914aaf

Tx prefix hash: a27849b0cf3d4b432d0af1b5d48a1343c1da343f9be139af2ef63eca6c72aaf9
Tx public key: 2b197f1b8dfbd6c4b7ac7b77324d4d9c14d0a268f6b3921267d6e57925e17f0a
Timestamp: 1710306886 Timestamp [UCT]: 2024-03-13 05:14:46 Age [y:d:h:m:s]: 01:096:22:08:14
Block: 977206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330176 RingCT/type: yes/0
Extra: 012b197f1b8dfbd6c4b7ac7b77324d4d9c14d0a268f6b3921267d6e57925e17f0a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e017ffefaf2940b562582f1c2fac468c43f1919e9392f75d56a3c965bb22547b 0.600000000000 1437207 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": 977216, "vin": [ { "gen": { "height": 977206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e017ffefaf2940b562582f1c2fac468c43f1919e9392f75d56a3c965bb22547b" } } ], "extra": [ 1, 43, 25, 127, 27, 141, 251, 214, 196, 183, 172, 123, 119, 50, 77, 77, 156, 20, 208, 162, 104, 246, 179, 146, 18, 103, 214, 229, 121, 37, 225, 127, 10, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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