Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 821413da3b56cca1636f46e6214367115a0e1db22c0d7ed0e180dec491d36778

Tx prefix hash: 40a4d9adbe407fd070cee1baf5bfed84b36ee9cf65c4d1150c95495fce7c7a20
Tx public key: e67f723aa2da4d5f0348e366f767cb7f747b154ce2adfdccab2f20cc3ddd7ed4
Timestamp: 1714374451 Timestamp [UCT]: 2024-04-29 07:07:31 Age [y:d:h:m:s]: 00:304:00:11:24
Block: 1010913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217286 RingCT/type: yes/0
Extra: 01e67f723aa2da4d5f0348e366f767cb7f747b154ce2adfdccab2f20cc3ddd7ed402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b98a0dd68be8a2785b2be17fa2fc10e0e30d892af9e936122f975706235cfd92 0.600000000000 1472995 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": 1010923, "vin": [ { "gen": { "height": 1010913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b98a0dd68be8a2785b2be17fa2fc10e0e30d892af9e936122f975706235cfd92" } } ], "extra": [ 1, 230, 127, 114, 58, 162, 218, 77, 95, 3, 72, 227, 102, 247, 103, 203, 127, 116, 123, 21, 76, 226, 173, 253, 204, 171, 47, 32, 204, 61, 221, 126, 212, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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