Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ddd07e75bdbcec1a41fefcc1b7761b595949e32ab07370edcdf249d2929502b

Tx prefix hash: 4d63cfd15d0969761c85fc907233ac1102197d1df61639af7b92c76b4f14886c
Tx public key: 4b6ed3f6c1e8d3df8eb7a9344b8a44a20d096439cae0967eadf263d99060bfbb
Timestamp: 1737098842 Timestamp [UCT]: 2025-01-17 07:27:22 Age [y:d:h:m:s]: 00:155:19:22:02
Block: 1199163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110991 RingCT/type: yes/0
Extra: 014b6ed3f6c1e8d3df8eb7a9344b8a44a20d096439cae0967eadf263d99060bfbb021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27912cda834e4e8f734a8404434b7a744863bea52ea63cadaeca30fde7ff656d 0.600000000000 1685792 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": 1199173, "vin": [ { "gen": { "height": 1199163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27912cda834e4e8f734a8404434b7a744863bea52ea63cadaeca30fde7ff656d" } } ], "extra": [ 1, 75, 110, 211, 246, 193, 232, 211, 223, 142, 183, 169, 52, 75, 138, 68, 162, 13, 9, 100, 57, 202, 224, 150, 126, 173, 242, 99, 217, 144, 96, 191, 187, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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