Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc52b3a6c8ef0edd1c73af69f21916d09023bcd7532d9ae98696e13708d453a0

Tx prefix hash: 5aa934a6cc00520133f5e312ada85d2faadb95bc4e3657f459a5b5a2e4eca6d2
Tx public key: 964e4c1a5dade89508aeaac6df2360c908ceed2146b703022a4ad8da439c14d1
Timestamp: 1764086967 Timestamp [UCT]: 2025-11-25 16:09:27 Age [y:d:h:m:s]: 00:009:20:27:05
Block: 1419931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7063 RingCT/type: yes/0
Extra: 01964e4c1a5dade89508aeaac6df2360c908ceed2146b703022a4ad8da439c14d10211000000028ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b30ab71b2e3cb0538ae3ed28b33fb3a57e4bc69f4426b53383a1270be22d77c2 0.600000000000 1908472 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": 1419941, "vin": [ { "gen": { "height": 1419931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b30ab71b2e3cb0538ae3ed28b33fb3a57e4bc69f4426b53383a1270be22d77c2" } } ], "extra": [ 1, 150, 78, 76, 26, 93, 173, 232, 149, 8, 174, 170, 198, 223, 35, 96, 201, 8, 206, 237, 33, 70, 183, 3, 2, 42, 74, 216, 218, 67, 156, 20, 209, 2, 17, 0, 0, 0, 2, 140, 235, 127, 9, 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