Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db5d37cd4d9e337049cdc0d94a1094a805a8a6983d5d4d45dbfdf258732adf95

Tx prefix hash: edd0accafae147cc089f403ac4a8188a80744fba8d7f045401e0ed5112a4de44
Tx public key: bdbef21ff10defe6eb5651b04afef4e2792cb69d4b2b6b65f281233e5940edb9
Timestamp: 1762615400 Timestamp [UCT]: 2025-11-08 15:23:20 Age [y:d:h:m:s]: 00:050:23:32:47
Block: 1407733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36508 RingCT/type: yes/0
Extra: 01bdbef21ff10defe6eb5651b04afef4e2792cb69d4b2b6b65f281233e5940edb9021100000005d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c3463d4eb70eae44bced1797c714dcbe4312fe745f701a363949f59b7a41e9b 0.600000000000 1896154 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": 1407743, "vin": [ { "gen": { "height": 1407733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c3463d4eb70eae44bced1797c714dcbe4312fe745f701a363949f59b7a41e9b" } } ], "extra": [ 1, 189, 190, 242, 31, 241, 13, 239, 230, 235, 86, 81, 176, 74, 254, 244, 226, 121, 44, 182, 157, 75, 43, 107, 101, 242, 129, 35, 62, 89, 64, 237, 185, 2, 17, 0, 0, 0, 5, 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