Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dc5ea2e8db3b6b6262cca6d4c6bbfaabf9be8dc9a64a138ad388b3e9ae6be89

Tx prefix hash: 6062fba77bce203bc8357cf84e60e858471ae76e093e3e2a2facb42002c855d4
Tx public key: 5efc95f5a52db0398a455a1a1e287fb351ac4c183067ffec393128eca383b2d9
Timestamp: 1710420760 Timestamp [UCT]: 2024-03-14 12:52:40 Age [y:d:h:m:s]: 01:008:23:03:37
Block: 978154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267381 RingCT/type: yes/0
Extra: 015efc95f5a52db0398a455a1a1e287fb351ac4c183067ffec393128eca383b2d902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e0587a35d4816804768a065f110d6dc2ad47e656b28b1dc6d1ec33636e640f0 0.600000000000 1438171 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": 978164, "vin": [ { "gen": { "height": 978154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e0587a35d4816804768a065f110d6dc2ad47e656b28b1dc6d1ec33636e640f0" } } ], "extra": [ 1, 94, 252, 149, 245, 165, 45, 176, 57, 138, 69, 90, 26, 30, 40, 127, 179, 81, 172, 76, 24, 48, 103, 255, 236, 57, 49, 40, 236, 163, 131, 178, 217, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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