Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4127fbadeda04d4605896e90566085f4e86aec2e95c92ba38205f2e8dc43688f

Tx prefix hash: 5ad02f25a062e9e6a0ca2d08bcc42e7fe5e87682d556aaa34587c7e357a50316
Tx public key: 3f38a27bcf2f1443ea37b2880712d874d26cfa6cd773e7802857fcacf6ccdaf5
Timestamp: 1719135410 Timestamp [UCT]: 2024-06-23 09:36:50 Age [y:d:h:m:s]: 00:326:12:43:40
Block: 1050368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233368 RingCT/type: yes/0
Extra: 013f38a27bcf2f1443ea37b2880712d874d26cfa6cd773e7802857fcacf6ccdaf50211000000060fbbc4c5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 070e216ea9d69ff81752ad36751a1630cbf81dd50376479d424bc13853bb7ff2 0.600000000000 1520533 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": 1050378, "vin": [ { "gen": { "height": 1050368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "070e216ea9d69ff81752ad36751a1630cbf81dd50376479d424bc13853bb7ff2" } } ], "extra": [ 1, 63, 56, 162, 123, 207, 47, 20, 67, 234, 55, 178, 136, 7, 18, 216, 116, 210, 108, 250, 108, 215, 115, 231, 128, 40, 87, 252, 172, 246, 204, 218, 245, 2, 17, 0, 0, 0, 6, 15, 187, 196, 197, 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