Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30014e6e2f1ad52208cb2be79748385ad73c14cddf7b947055e183b3e2503ef7

Tx prefix hash: e72628b51907181908eeef39278acfce7db963da0ab4820e643ef4036251a522
Tx public key: b0b70f9cdf44328c1ec74ea87ed5030c35c5cdc0caad42c18fdc4026ef77f85a
Timestamp: 1753210257 Timestamp [UCT]: 2025-07-22 18:50:57 Age [y:d:h:m:s]: 00:116:04:32:32
Block: 1331136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81851 RingCT/type: yes/0
Extra: 01b0b70f9cdf44328c1ec74ea87ed5030c35c5cdc0caad42c18fdc4026ef77f85a021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db6082e9dcb4f4f5ec7e17bd09f4103a1fe19aefba7faa8e3892cf118c76538f 0.600000000000 1818929 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": 1331146, "vin": [ { "gen": { "height": 1331136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db6082e9dcb4f4f5ec7e17bd09f4103a1fe19aefba7faa8e3892cf118c76538f" } } ], "extra": [ 1, 176, 183, 15, 156, 223, 68, 50, 140, 30, 199, 78, 168, 126, 213, 3, 12, 53, 197, 205, 192, 202, 173, 66, 193, 143, 220, 64, 38, 239, 119, 248, 90, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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