Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60dd953d3366cd8b245f6e8c79b7af2cbabea52693b24c8c80c33a9482789401

Tx prefix hash: d80237c33fe6f30e298e7ade53ca61354ea63dbe89f2e695e48a9f9e879271ca
Tx public key: 0080092be5fd83b565c3198d7ba08f3279fa085daab0a6e090e7db092b45fba7
Timestamp: 1674278771 Timestamp [UCT]: 2023-01-21 05:26:11 Age [y:d:h:m:s]: 01:364:08:36:38
Block: 679366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521385 RingCT/type: yes/0
Extra: 010080092be5fd83b565c3198d7ba08f3279fa085daab0a6e090e7db092b45fba70211000000015029cbac000000000000000000

1 output(s) for total of 3.443327787000 dcy

stealth address amount amount idx
00: 8b941c7085c0a105f6a889cfdf94771bb70fc774c3d4e1ce493d65404ad6bd85 3.443327787000 1121341 of 0

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": 679376, "vin": [ { "gen": { "height": 679366 } } ], "vout": [ { "amount": 3443327787, "target": { "key": "8b941c7085c0a105f6a889cfdf94771bb70fc774c3d4e1ce493d65404ad6bd85" } } ], "extra": [ 1, 0, 128, 9, 43, 229, 253, 131, 181, 101, 195, 25, 141, 123, 160, 143, 50, 121, 250, 8, 93, 170, 176, 166, 224, 144, 231, 219, 9, 43, 69, 251, 167, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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