Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 820d2eb95786e28070c8d7793008b5a43b1103b582b9d37d9cf2f0b0490c6c5f

Tx prefix hash: 946d4962686baae3cdcb3d955bc60498baabdc1dc2599d655d13f7b6703c2fdb
Tx public key: c249e342805ef1eb41298490daf62598c9441b67f3f752876c5f7581ef65f6ae
Timestamp: 1703099151 Timestamp [UCT]: 2023-12-20 19:05:51 Age [y:d:h:m:s]: 01:331:23:32:34
Block: 917458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496103 RingCT/type: yes/0
Extra: 01c249e342805ef1eb41298490daf62598c9441b67f3f752876c5f7581ef65f6ae02110000000479bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 604293716b54b65ac96d6023f901aa270d0f50576cb44b6aa971fc6c202fd9c4 0.600000000000 1375040 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": 917468, "vin": [ { "gen": { "height": 917458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "604293716b54b65ac96d6023f901aa270d0f50576cb44b6aa971fc6c202fd9c4" } } ], "extra": [ 1, 194, 73, 227, 66, 128, 94, 241, 235, 65, 41, 132, 144, 218, 246, 37, 152, 201, 68, 27, 103, 243, 247, 82, 135, 108, 95, 117, 129, 239, 101, 246, 174, 2, 17, 0, 0, 0, 4, 121, 189, 163, 190, 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