Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fbb6bd60098618f6edab648797b7046e5bdc8ea4a46c2b1a379623297914447

Tx prefix hash: 8bb0c69504ca295190a1fd07951cb353ec02a367b3f0c4ba2bded3d156230816
Tx public key: e165173def3f2dffca20421ed2830fd8436a621e6956c85f405b17cd445c172a
Timestamp: 1714744044 Timestamp [UCT]: 2024-05-03 13:47:24 Age [y:d:h:m:s]: 00:340:09:42:40
Block: 1013990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243315 RingCT/type: yes/0
Extra: 01e165173def3f2dffca20421ed2830fd8436a621e6956c85f405b17cd445c172a0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dfb24a7bf747daf243d4efbc2172e1a2bc7c9d22e3a8cdad4b8ac827bfbaa56 0.600000000000 1476953 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": 1014000, "vin": [ { "gen": { "height": 1013990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dfb24a7bf747daf243d4efbc2172e1a2bc7c9d22e3a8cdad4b8ac827bfbaa56" } } ], "extra": [ 1, 225, 101, 23, 61, 239, 63, 45, 255, 202, 32, 66, 30, 210, 131, 15, 216, 67, 106, 98, 30, 105, 86, 200, 95, 64, 91, 23, 205, 68, 92, 23, 42, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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