Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3859b3bbeec613ad2ff7265c2f1496ecb8afb6756169c23cc18b1325ab2bdd6e

Tx prefix hash: 30dbbb856cb871180611e7e8467764ce4c3d177958678807c775b971ec612453
Tx public key: da5e2269429416ec17716cae638402a68fa5fb447a1d4fe5b5e70fa32a23b0c8
Timestamp: 1649905897 Timestamp [UCT]: 2022-04-14 03:11:37 Age [y:d:h:m:s]: 02:220:21:26:42
Block: 479739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 677736 RingCT/type: yes/0
Extra: 01da5e2269429416ec17716cae638402a68fa5fb447a1d4fe5b5e70fa32a23b0c8021100000001a8c141c5000000000000000000

1 output(s) for total of 15.791587064000 dcy

stealth address amount amount idx
00: 5758e60664c6cf015f375d277fd171839dd55d91d75d8f73d6328a2e1f1e8240 15.791587064000 900692 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": 479749, "vin": [ { "gen": { "height": 479739 } } ], "vout": [ { "amount": 15791587064, "target": { "key": "5758e60664c6cf015f375d277fd171839dd55d91d75d8f73d6328a2e1f1e8240" } } ], "extra": [ 1, 218, 94, 34, 105, 66, 148, 22, 236, 23, 113, 108, 174, 99, 132, 2, 166, 143, 165, 251, 68, 122, 29, 79, 229, 181, 231, 15, 163, 42, 35, 176, 200, 2, 17, 0, 0, 0, 1, 168, 193, 65, 197, 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