Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b67d52b5a57823c9d6810b52032cf66a25e1490007e7975283a4927525f7663f

Tx prefix hash: 5dfffc9d9ccbdb73791c2251754201ef3c1a2f0a60eef631356e161e4693f6b1
Tx public key: 0153fbf5a5bc7cc3c4db6c1b3e47975867acdc78598dff0fa5a5457839994e8b
Timestamp: 1723003241 Timestamp [UCT]: 2024-08-07 04:00:41 Age [y:d:h:m:s]: 00:144:14:18:51
Block: 1082449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103441 RingCT/type: yes/0
Extra: 010153fbf5a5bc7cc3c4db6c1b3e47975867acdc78598dff0fa5a5457839994e8b021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 501c7bb85b1a86b78ff670b200893125e5cda6d6bb360b1264a8b7191502f3bf 0.600000000000 1556276 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": 1082459, "vin": [ { "gen": { "height": 1082449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "501c7bb85b1a86b78ff670b200893125e5cda6d6bb360b1264a8b7191502f3bf" } } ], "extra": [ 1, 1, 83, 251, 245, 165, 188, 124, 195, 196, 219, 108, 27, 62, 71, 151, 88, 103, 172, 220, 120, 89, 141, 255, 15, 165, 165, 69, 120, 57, 153, 78, 139, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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