Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 472469b39e5bc187f8ac5044eec71718662c49051b2e0ff48b0cb3ea2a451a6e

Tx prefix hash: 4fc17fc42cdf03e655d36f29c7860f2e4cad037a8a46c1302761d2992efbc691
Tx public key: df0c8431c5c1525a012c95a947376990de1ef2901d9ab3849a4b0ce278c7b92a
Timestamp: 1723147788 Timestamp [UCT]: 2024-08-08 20:09:48 Age [y:d:h:m:s]: 01:091:06:17:52
Block: 1083648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323700 RingCT/type: yes/0
Extra: 01df0c8431c5c1525a012c95a947376990de1ef2901d9ab3849a4b0ce278c7b92a021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c13db21464090d5d12b663082a4594ce055f8fd1ba01dd8f5323dd5a92a57763 0.600000000000 1557643 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": 1083658, "vin": [ { "gen": { "height": 1083648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c13db21464090d5d12b663082a4594ce055f8fd1ba01dd8f5323dd5a92a57763" } } ], "extra": [ 1, 223, 12, 132, 49, 197, 193, 82, 90, 1, 44, 149, 169, 71, 55, 105, 144, 222, 30, 242, 144, 29, 154, 179, 132, 154, 75, 12, 226, 120, 199, 185, 42, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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