Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8a4b6c8458762142d2e308ad1cfe0ae26a98633c6a7fbc3999cc541a4666c11

Tx prefix hash: 1c5f24a2e4b03444012cd962419c4d5ca6911061f343be98fa182e8b257792bd
Tx public key: e511f4c8ad29576e94983dbef5f655bc9f5dbb2bf486262977a4a73e5bac3ee1
Timestamp: 1664200102 Timestamp [UCT]: 2022-09-26 13:48:22 Age [y:d:h:m:s]: 02:230:04:15:37
Block: 596264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 685931 RingCT/type: yes/0
Extra: 01e511f4c8ad29576e94983dbef5f655bc9f5dbb2bf486262977a4a73e5bac3ee1021100000001798ce684000000000000000000

1 output(s) for total of 6.491493566000 dcy

stealth address amount amount idx
00: 1ea90a598e089451a2453fd29279087bb2d97ffd00aa481d86a798d541f92399 6.491493566000 1031461 of 0

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": 596274, "vin": [ { "gen": { "height": 596264 } } ], "vout": [ { "amount": 6491493566, "target": { "key": "1ea90a598e089451a2453fd29279087bb2d97ffd00aa481d86a798d541f92399" } } ], "extra": [ 1, 229, 17, 244, 200, 173, 41, 87, 110, 148, 152, 61, 190, 245, 246, 85, 188, 159, 93, 187, 43, 244, 134, 38, 41, 119, 164, 167, 62, 91, 172, 62, 225, 2, 17, 0, 0, 0, 1, 121, 140, 230, 132, 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