Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a81a09f61023e89673248c8091f2c0e51dbb92fc2d31d7a26624b99d0832ab47

Tx prefix hash: fb7baab0b3e5febf32d765d13317236765245e23dce29e9cc4aba360a814a740
Tx public key: 9ab9f21a09561fb5d27a580fcff7ed4297a43d78e5213f1e7d39e354115ccae0
Timestamp: 1718794613 Timestamp [UCT]: 2024-06-19 10:56:53 Age [y:d:h:m:s]: 00:360:19:41:43
Block: 1047577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257787 RingCT/type: yes/0
Extra: 019ab9f21a09561fb5d27a580fcff7ed4297a43d78e5213f1e7d39e354115ccae00211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71208abf43b97a8edc2019470fb40954fff10eb25e40b4e1cb47f829bb6eae20 0.600000000000 1517434 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": 1047587, "vin": [ { "gen": { "height": 1047577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71208abf43b97a8edc2019470fb40954fff10eb25e40b4e1cb47f829bb6eae20" } } ], "extra": [ 1, 154, 185, 242, 26, 9, 86, 31, 181, 210, 122, 88, 15, 207, 247, 237, 66, 151, 164, 61, 120, 229, 33, 63, 30, 125, 57, 227, 84, 17, 92, 202, 224, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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