Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5b2e028ae566e8a38b5f3e8308ed35d4a828eaaf86aa46b4ef4a8da78fdab15

Tx prefix hash: d1f2067eb7489af1142baed573f27dfaf66f58056cafeb7e4e4f193fa223026e
Tx public key: 984205236703e464040f0a403a0bac30224ff24e919287087742b40b2f6d9e4f
Timestamp: 1735150379 Timestamp [UCT]: 2024-12-25 18:12:59 Age [y:d:h:m:s]: 00:107:08:10:59
Block: 1183042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76510 RingCT/type: yes/0
Extra: 01984205236703e464040f0a403a0bac30224ff24e919287087742b40b2f6d9e4f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1c4b15c864cb1a626a5d141144489dc041ec35a006f86887f3d0ea994dd1606 0.600000000000 1669481 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": 1183052, "vin": [ { "gen": { "height": 1183042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1c4b15c864cb1a626a5d141144489dc041ec35a006f86887f3d0ea994dd1606" } } ], "extra": [ 1, 152, 66, 5, 35, 103, 3, 228, 100, 4, 15, 10, 64, 58, 11, 172, 48, 34, 79, 242, 78, 145, 146, 135, 8, 119, 66, 180, 11, 47, 109, 158, 79, 2, 17, 0, 0, 0, 4, 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