Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edb78599c0f369ddb61175a147ef9ffa5adc8d8d0a208a9b2c9c6a34b51ac6cc

Tx prefix hash: db89a1bedd2645fc2f9669f71af49acfd7bdaa6d6219f9914d8e500892523069
Tx public key: e5b62d6e8b906f13456b64735e3c101c89d9b7536c3cc0136caca2cd3e657b10
Timestamp: 1711589536 Timestamp [UCT]: 2024-03-28 01:32:16 Age [y:d:h:m:s]: 01:306:22:40:29
Block: 987842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477976 RingCT/type: yes/0
Extra: 01e5b62d6e8b906f13456b64735e3c101c89d9b7536c3cc0136caca2cd3e657b100211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a24a30243c1ecde55e34b06547d6679852b96e5aa500f44be3b21aabf07c044 0.600000000000 1448103 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": 987852, "vin": [ { "gen": { "height": 987842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a24a30243c1ecde55e34b06547d6679852b96e5aa500f44be3b21aabf07c044" } } ], "extra": [ 1, 229, 182, 45, 110, 139, 144, 111, 19, 69, 107, 100, 115, 94, 60, 16, 28, 137, 217, 183, 83, 108, 60, 192, 19, 108, 172, 162, 205, 62, 101, 123, 16, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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