Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e3d9445947d3e426bcdf3198b097b6dfae440854bf20f34da9382c0d0f448be

Tx prefix hash: 73a7c461e15a9e81adb45c9aae38280035e070f6a9453c9d071b8b5e6d9d8685
Tx public key: 4b8663b4fb57a6a423c754fabd77efb0bd2517ddca65d4c62262008158bb8797
Timestamp: 1736611026 Timestamp [UCT]: 2025-01-11 15:57:06 Age [y:d:h:m:s]: 00:158:07:48:02
Block: 1195126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112848 RingCT/type: yes/0
Extra: 014b8663b4fb57a6a423c754fabd77efb0bd2517ddca65d4c62262008158bb8797021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 899e1e8328b39a5e41cc338dfa32b4fca999d19906fb5e8305405b1d1a0baf43 0.600000000000 1681713 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": 1195136, "vin": [ { "gen": { "height": 1195126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "899e1e8328b39a5e41cc338dfa32b4fca999d19906fb5e8305405b1d1a0baf43" } } ], "extra": [ 1, 75, 134, 99, 180, 251, 87, 166, 164, 35, 199, 84, 250, 189, 119, 239, 176, 189, 37, 23, 221, 202, 101, 212, 198, 34, 98, 0, 129, 88, 187, 135, 151, 2, 17, 0, 0, 0, 1, 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