Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 226b8749d3c641dc7d37762116f250197132bfaf7f8bc34f2f319d76b04fdb7c

Tx prefix hash: caa91222de50afa693a9474249ad36e07349b5f8aac144217ce6876990f51276
Tx public key: a8f087417a2b85fd28bed082c4fffe2d9eec7b19e5ed8dd6da024bbcdf2f3a4a
Timestamp: 1737436411 Timestamp [UCT]: 2025-01-21 05:13:31 Age [y:d:h:m:s]: 00:349:18:52:02
Block: 1201912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247628 RingCT/type: yes/0
Extra: 01a8f087417a2b85fd28bed082c4fffe2d9eec7b19e5ed8dd6da024bbcdf2f3a4a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d119969c3054524ef066a9793818ca17edd1aeb433c50361dd2cc818d5a4e32 0.600000000000 1688571 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": 1201922, "vin": [ { "gen": { "height": 1201912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d119969c3054524ef066a9793818ca17edd1aeb433c50361dd2cc818d5a4e32" } } ], "extra": [ 1, 168, 240, 135, 65, 122, 43, 133, 253, 40, 190, 208, 130, 196, 255, 254, 45, 158, 236, 123, 25, 229, 237, 141, 214, 218, 2, 75, 188, 223, 47, 58, 74, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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