Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90ad362564ba84f6aa003c8936d43ccf82e673443845e2361f33b23370d4bd1e

Tx prefix hash: 569ded64ba86e071d88c46e92d9e06b26cee1f1d0884757643c43c2668a149e1
Tx public key: a98b7431eec342fdf6360b78de9c478e40f566d15cbc8dfbe9ac1ccf3a33b0a2
Timestamp: 1746452845 Timestamp [UCT]: 2025-05-05 13:47:25 Age [y:d:h:m:s]: 00:192:10:10:50
Block: 1276335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135242 RingCT/type: yes/0
Extra: 01a98b7431eec342fdf6360b78de9c478e40f566d15cbc8dfbe9ac1ccf3a33b0a20211000000011f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7abce2e55336ad1fbf2435af3a4b07c8f389f4d3270e551f2f5e94553985a841 0.600000000000 1763670 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": 1276345, "vin": [ { "gen": { "height": 1276335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7abce2e55336ad1fbf2435af3a4b07c8f389f4d3270e551f2f5e94553985a841" } } ], "extra": [ 1, 169, 139, 116, 49, 238, 195, 66, 253, 246, 54, 11, 120, 222, 156, 71, 142, 64, 245, 102, 209, 92, 188, 141, 251, 233, 172, 28, 207, 58, 51, 176, 162, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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