Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b63c6d2005e1869885af724bff10c7214bb3aea991b7f40409c9599c977bb34

Tx prefix hash: 0688f3c67c6fd82c7a332c0008f86b28832f2f8536502906efdbcf439e014cc3
Tx public key: af80f387eb1fc2dcaa5115348c51724ae343529cd79ee29e33d411e7728f8c5e
Timestamp: 1638198580 Timestamp [UCT]: 2021-11-29 15:09:40 Age [y:d:h:m:s]: 03:105:15:45:47
Block: 384736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 854214 RingCT/type: yes/0
Extra: 01af80f387eb1fc2dcaa5115348c51724ae343529cd79ee29e33d411e7728f8c5e02110000000106faf294000000000000000000

1 output(s) for total of 32.599451601000 dcy

stealth address amount amount idx
00: 3a5e98702090360f8e81d10b242b8e7ec1bf22e0c98b9e112be14b8e3253814c 32.599451601000 776507 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": 384746, "vin": [ { "gen": { "height": 384736 } } ], "vout": [ { "amount": 32599451601, "target": { "key": "3a5e98702090360f8e81d10b242b8e7ec1bf22e0c98b9e112be14b8e3253814c" } } ], "extra": [ 1, 175, 128, 243, 135, 235, 31, 194, 220, 170, 81, 21, 52, 140, 81, 114, 74, 227, 67, 82, 156, 215, 158, 226, 158, 51, 212, 17, 231, 114, 143, 140, 94, 2, 17, 0, 0, 0, 1, 6, 250, 242, 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