Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6bcac740bc649bbfeab693d04d5ef25702844e402aa650764978cc5b51f7477

Tx prefix hash: dd33b1e18e519900b4e17ee94bfc268dbcaa9533cc0360f5dfca3c28bbbc28d2
Tx public key: 4a12b6ed8b28fd715555d57cb13e19b41184f9978873b4ae945fa756b883a46c
Timestamp: 1733789139 Timestamp [UCT]: 2024-12-10 00:05:39 Age [y:d:h:m:s]: 00:190:12:10:23
Block: 1171777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135876 RingCT/type: yes/0
Extra: 014a12b6ed8b28fd715555d57cb13e19b41184f9978873b4ae945fa756b883a46c0211000000171f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56ef27a756d15ae49d7e707356c5c773c5142e8d1cbcca39496e4ae80dd35588 0.600000000000 1657578 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": 1171787, "vin": [ { "gen": { "height": 1171777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56ef27a756d15ae49d7e707356c5c773c5142e8d1cbcca39496e4ae80dd35588" } } ], "extra": [ 1, 74, 18, 182, 237, 139, 40, 253, 113, 85, 85, 213, 124, 177, 62, 25, 180, 17, 132, 249, 151, 136, 115, 180, 174, 148, 95, 167, 86, 184, 131, 164, 108, 2, 17, 0, 0, 0, 23, 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