Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d338abcdba3ec145701e1ba6a432d1fc52802179bc340f3dd2974987226eb28d

Tx prefix hash: ad6a7a60c27364b72ec0a35e69c2dc6a712a9762c14a1a3d581b230dc2c76ea3
Tx public key: 51dd030d0f3aa8241b4e84779e1c629c1a9ff07eaea39678e9a7ab416475b3d5
Timestamp: 1709331563 Timestamp [UCT]: 2024-03-01 22:19:23 Age [y:d:h:m:s]: 01:090:04:58:21
Block: 969113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325514 RingCT/type: yes/0
Extra: 0151dd030d0f3aa8241b4e84779e1c629c1a9ff07eaea39678e9a7ab416475b3d50211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e36de7581116dd426fffc1d9b564f724f12f84e0d004ff5ffca80745ddfb0b0e 0.600000000000 1428940 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": 969123, "vin": [ { "gen": { "height": 969113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e36de7581116dd426fffc1d9b564f724f12f84e0d004ff5ffca80745ddfb0b0e" } } ], "extra": [ 1, 81, 221, 3, 13, 15, 58, 168, 36, 27, 78, 132, 119, 158, 28, 98, 156, 26, 159, 240, 126, 174, 163, 150, 120, 233, 167, 171, 65, 100, 117, 179, 213, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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