Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 469d599f5e4006ced1734c2f06cad2f71a304077fe2e7eb3126445ee3beeb734

Tx prefix hash: 30a37d562274db90de09c95ccc02967a550a77bd34b4435e0f4bd83ec068b630
Tx public key: 88cdd1c3c1c22355b66b6d81399ab4e3290ab4b5fd44dc8c32fd1a3d70fc8a77
Timestamp: 1749699678 Timestamp [UCT]: 2025-06-12 03:41:18 Age [y:d:h:m:s]: 00:154:15:37:41
Block: 1303186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108240 RingCT/type: yes/0
Extra: 0188cdd1c3c1c22355b66b6d81399ab4e3290ab4b5fd44dc8c32fd1a3d70fc8a77021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d707e19a90ef9c294dc5c7c2be9bdb7af18b7c025d756d4b95dc6876e42ab201 0.600000000000 1790761 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": 1303196, "vin": [ { "gen": { "height": 1303186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d707e19a90ef9c294dc5c7c2be9bdb7af18b7c025d756d4b95dc6876e42ab201" } } ], "extra": [ 1, 136, 205, 209, 195, 193, 194, 35, 85, 182, 107, 109, 129, 57, 154, 180, 227, 41, 10, 180, 181, 253, 68, 220, 140, 50, 253, 26, 61, 112, 252, 138, 119, 2, 17, 0, 0, 0, 2, 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