Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55b2fdd7b02db3e74984f4afcbdbe6221d2d4b423a3e82c0e6472905cfa633a7

Tx prefix hash: 678cc76ab2567ca991fc475cbf15595e5cc6ef93ddd6fc95d4d495e290d997ca
Tx public key: 2abf80e225e7cd0d0c363fddd343665be0d30a2d400804e2291342e8e2993940
Timestamp: 1762622436 Timestamp [UCT]: 2025-11-08 17:20:36 Age [y:d:h:m:s]: 00:055:14:13:13
Block: 1407788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39814 RingCT/type: yes/0
Extra: 012abf80e225e7cd0d0c363fddd343665be0d30a2d400804e2291342e8e2993940021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf3c3df95b5611c4668c4c4c809b6336c33514fcc665627fe35f742cae34dd48 0.600000000000 1896209 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": 1407798, "vin": [ { "gen": { "height": 1407788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf3c3df95b5611c4668c4c4c809b6336c33514fcc665627fe35f742cae34dd48" } } ], "extra": [ 1, 42, 191, 128, 226, 37, 231, 205, 13, 12, 54, 63, 221, 211, 67, 102, 91, 224, 211, 10, 45, 64, 8, 4, 226, 41, 19, 66, 232, 226, 153, 57, 64, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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