Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10ffd70b6acf9babc9c79fd9c2b004cebf0eef00b989d773fcbc2662804349c6

Tx prefix hash: 6cab3bc715ac2439930f6ff320fb0d13511995ebe04e9915a52553449d3a7159
Tx public key: 07588fb3d52e7b3aa316aebadb57e90458257867840401d3d2fcf2a62eb4df8d
Timestamp: 1729870509 Timestamp [UCT]: 2024-10-25 15:35:09 Age [y:d:h:m:s]: 00:063:17:37:45
Block: 1139348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45561 RingCT/type: yes/0
Extra: 0107588fb3d52e7b3aa316aebadb57e90458257867840401d3d2fcf2a62eb4df8d0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f55097f078806cff6a6419ee5106bfc297ea88c3a784114356f2cd6d09938727 0.600000000000 1623135 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": 1139358, "vin": [ { "gen": { "height": 1139348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f55097f078806cff6a6419ee5106bfc297ea88c3a784114356f2cd6d09938727" } } ], "extra": [ 1, 7, 88, 143, 179, 213, 46, 123, 58, 163, 22, 174, 186, 219, 87, 233, 4, 88, 37, 120, 103, 132, 4, 1, 211, 210, 252, 242, 166, 46, 180, 223, 141, 2, 17, 0, 0, 0, 6, 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