Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0dad09ef7b9d89ffd9d4c1ff0a1d314e7d3319486aab0bb7a98cc7aea6d0a45

Tx prefix hash: 5431076003a5edcdb725fce0b733c42971faee8d46060c75f4984507f15e946b
Tx public key: 7dcd54a901d38c8aed602bb3f6396331592d8242e6d4287486cb0b79cfef22bb
Timestamp: 1751486880 Timestamp [UCT]: 2025-07-02 20:08:00 Age [y:d:h:m:s]: 00:141:05:21:30
Block: 1317448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99167 RingCT/type: yes/0
Extra: 017dcd54a901d38c8aed602bb3f6396331592d8242e6d4287486cb0b79cfef22bb0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c980bb2cc53dd8f14b6a9c06e9ad38273b238a021b620c434a36417cc226b11 0.600000000000 1805115 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": 1317458, "vin": [ { "gen": { "height": 1317448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c980bb2cc53dd8f14b6a9c06e9ad38273b238a021b620c434a36417cc226b11" } } ], "extra": [ 1, 125, 205, 84, 169, 1, 211, 140, 138, 237, 96, 43, 179, 246, 57, 99, 49, 89, 45, 130, 66, 230, 212, 40, 116, 134, 203, 11, 121, 207, 239, 34, 187, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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