Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b415f22c6c4ad34d28bbadc982d00a55ed154be3067f2d6cc3a0be7c0e1a874a

Tx prefix hash: 29de9bf9211df417c35865871427917348e7b152f7eabf99396062305076c5a3
Tx public key: d615485129ba34ed64b84f1fbf52b5cd57c4dc45e5beebac94802cbe68a01433
Timestamp: 1765907720 Timestamp [UCT]: 2025-12-16 17:55:20 Age [y:d:h:m:s]: 00:009:05:00:49
Block: 1435008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6599 RingCT/type: yes/0
Extra: 01d615485129ba34ed64b84f1fbf52b5cd57c4dc45e5beebac94802cbe68a01433021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb884d8bf6eabd45101922d7d25e613b0ad740c8e7ea3d60dc774f861f7315a8 0.600000000000 1923805 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": 1435018, "vin": [ { "gen": { "height": 1435008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb884d8bf6eabd45101922d7d25e613b0ad740c8e7ea3d60dc774f861f7315a8" } } ], "extra": [ 1, 214, 21, 72, 81, 41, 186, 52, 237, 100, 184, 79, 31, 191, 82, 181, 205, 87, 196, 220, 69, 229, 190, 235, 172, 148, 128, 44, 190, 104, 160, 20, 51, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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