Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebabbda451070b0b852bcba00b3d32ce3024fdf49516401c68b216deb5e7fd5d

Tx prefix hash: 4cd73a0e5b96d0cab44c14fff6a0c62dda8fc3b9239439128a81392baf35c589
Tx public key: c972c862b54d3325f54ad0ee525b5dfac1f8ab317e314833b05fd24180185460
Timestamp: 1735286815 Timestamp [UCT]: 2024-12-27 08:06:55 Age [y:d:h:m:s]: 00:105:14:47:31
Block: 1184156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75290 RingCT/type: yes/0
Extra: 01c972c862b54d3325f54ad0ee525b5dfac1f8ab317e314833b05fd241801854600211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e3df07a9ccc7799ff1d942ca7c45a1105e2daebe5adf50c62aa7e658fd7e564 0.600000000000 1670609 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": 1184166, "vin": [ { "gen": { "height": 1184156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e3df07a9ccc7799ff1d942ca7c45a1105e2daebe5adf50c62aa7e658fd7e564" } } ], "extra": [ 1, 201, 114, 200, 98, 181, 77, 51, 37, 245, 74, 208, 238, 82, 91, 93, 250, 193, 248, 171, 49, 126, 49, 72, 51, 176, 95, 210, 65, 128, 24, 84, 96, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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