Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea617f12cdd6865cf8b3cbe64e3807e943d5e0ae0f042620da7acf875b9d4329

Tx prefix hash: a260a531a82de191961cc7929b0ceb5ec1951bbe3653f057e37fc53798cfd57d
Tx public key: 51e36736cdfa30f451ebc3f7cf46e594844b5904c12f0454e8e5e834f5fd3d25
Timestamp: 1721233719 Timestamp [UCT]: 2024-07-17 16:28:39 Age [y:d:h:m:s]: 00:129:22:50:35
Block: 1067796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92984 RingCT/type: yes/0
Extra: 0151e36736cdfa30f451ebc3f7cf46e594844b5904c12f0454e8e5e834f5fd3d2502110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 229c27687a61781fcb7e282293cf2d514244402f0eecb8edfdd12bd0c945e512 0.600000000000 1538711 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": 1067806, "vin": [ { "gen": { "height": 1067796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "229c27687a61781fcb7e282293cf2d514244402f0eecb8edfdd12bd0c945e512" } } ], "extra": [ 1, 81, 227, 103, 54, 205, 250, 48, 244, 81, 235, 195, 247, 207, 70, 229, 148, 132, 75, 89, 4, 193, 47, 4, 84, 232, 229, 232, 52, 245, 253, 61, 37, 2, 17, 0, 0, 0, 9, 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