Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8d3f9c68b2ec3d7572da6c1a0fcb7155d6214bc7120be5905d50244d176b30f

Tx prefix hash: 09063e82d9b0fcc857ce5109ae64c5524a820d6998436ef52c2126f6020db780
Tx public key: cacba416d6e8d049b39818b9fdd4b73bc4e32381a13b592fe7cf501b68c7705c
Timestamp: 1724555146 Timestamp [UCT]: 2024-08-25 03:05:46 Age [y:d:h:m:s]: 01:076:10:46:25
Block: 1095348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313063 RingCT/type: yes/0
Extra: 01cacba416d6e8d049b39818b9fdd4b73bc4e32381a13b592fe7cf501b68c7705c02110000001191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fde49290a51355cfddbc5b057ac0b02f306efa38692603453bce313d3d58484e 0.600000000000 1570513 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": 1095358, "vin": [ { "gen": { "height": 1095348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fde49290a51355cfddbc5b057ac0b02f306efa38692603453bce313d3d58484e" } } ], "extra": [ 1, 202, 203, 164, 22, 214, 232, 208, 73, 179, 152, 24, 185, 253, 212, 183, 59, 196, 227, 35, 129, 161, 59, 89, 47, 231, 207, 80, 27, 104, 199, 112, 92, 2, 17, 0, 0, 0, 17, 145, 225, 60, 4, 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