Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 451d73caa9694f532a71df0e90bd2edb84945d508d77c5ab1ad0ee8493a9d937

Tx prefix hash: 632d45160a730871ee345afc76a6dde263bfc37d8304e1360fd8eb786dfc44cf
Tx public key: efb8e4f5f25a08b6c606d516f27fa45263a571cec8edf784184e40f8c8719561
Timestamp: 1757295771 Timestamp [UCT]: 2025-09-08 01:42:51 Age [y:d:h:m:s]: 00:106:22:01:31
Block: 1363734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76451 RingCT/type: yes/0
Extra: 01efb8e4f5f25a08b6c606d516f27fa45263a571cec8edf784184e40f8c8719561021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 085addc14dcbe4fabecdbfb816c3298561efdc7b01ae580f2033dcb6c03d61e8 0.600000000000 1851773 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": 1363744, "vin": [ { "gen": { "height": 1363734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "085addc14dcbe4fabecdbfb816c3298561efdc7b01ae580f2033dcb6c03d61e8" } } ], "extra": [ 1, 239, 184, 228, 245, 242, 90, 8, 182, 198, 6, 213, 22, 242, 127, 164, 82, 99, 165, 113, 206, 200, 237, 247, 132, 24, 78, 64, 248, 200, 113, 149, 97, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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