Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef04f6ea534eb25d899148ed918ddecb77e46744c77789566f58b8b3d004abe8

Tx prefix hash: f8ae01fbd2d7ebdde918640444ba3682ac0ea4f110716afc737e8640ed0ab10d
Tx public key: 8d378be8022172b3ea335b5f803aa0ac2e86a1cae98c456d9501e4ea14708400
Timestamp: 1725445562 Timestamp [UCT]: 2024-09-04 10:26:02 Age [y:d:h:m:s]: 00:209:05:24:26
Block: 1102708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149360 RingCT/type: yes/0
Extra: 018d378be8022172b3ea335b5f803aa0ac2e86a1cae98c456d9501e4ea1470840002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10b8292ffc5fd1e6dbb05746aea244d77cc10c5aa824d7de81e8ed6bfb574095 0.600000000000 1579247 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": 1102718, "vin": [ { "gen": { "height": 1102708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10b8292ffc5fd1e6dbb05746aea244d77cc10c5aa824d7de81e8ed6bfb574095" } } ], "extra": [ 1, 141, 55, 139, 232, 2, 33, 114, 179, 234, 51, 91, 95, 128, 58, 160, 172, 46, 134, 161, 202, 233, 140, 69, 109, 149, 1, 228, 234, 20, 112, 132, 0, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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