Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4111b3ca7d72ad40685dc73b2390d8bcaeafaf816da2f1a0c1322873d0402400

Tx prefix hash: f55b22cf32f62b5ec886ff2ef9015f470f611e11d932d871bf6deb6fd2fd10ae
Tx public key: ee288c1ce9400506927607a7ef1a3b413b845883f0fdd56a87fe43b7aed6390a
Timestamp: 1703005393 Timestamp [UCT]: 2023-12-19 17:03:13 Age [y:d:h:m:s]: 01:120:21:32:09
Block: 916674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347531 RingCT/type: yes/0
Extra: 01ee288c1ce9400506927607a7ef1a3b413b845883f0fdd56a87fe43b7aed6390a021100000004e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab444f8a8a521c690bc6a685fedba2766d3e90b3db741f0937b35a679acc25d9 0.600000000000 1374234 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": 916684, "vin": [ { "gen": { "height": 916674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab444f8a8a521c690bc6a685fedba2766d3e90b3db741f0937b35a679acc25d9" } } ], "extra": [ 1, 238, 40, 140, 28, 233, 64, 5, 6, 146, 118, 7, 167, 239, 26, 59, 65, 59, 132, 88, 131, 240, 253, 213, 106, 135, 254, 67, 183, 174, 214, 57, 10, 2, 17, 0, 0, 0, 4, 228, 187, 107, 131, 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