Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27c12ab0ed6ab05fc2f21416760600e41fcfe637c0c7128fda597a7506cb0b68

Tx prefix hash: b762cb63c926a70b9b15e0bca952354c7706e1e818dfcefd40853aa538c2abc0
Tx public key: 0082880d4936dc8fc327ab7558294c4448dc5fc504bec1f0fc2d7c5fd0281b66
Timestamp: 1721117582 Timestamp [UCT]: 2024-07-16 08:13:02 Age [y:d:h:m:s]: 00:222:11:41:29
Block: 1066838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158879 RingCT/type: yes/0
Extra: 010082880d4936dc8fc327ab7558294c4448dc5fc504bec1f0fc2d7c5fd0281b66021100000012e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8d628352d1f0cca6d6912d771ee6391e451dc6f21c5d981fa8075495d62efe1 0.600000000000 1537507 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": 1066848, "vin": [ { "gen": { "height": 1066838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8d628352d1f0cca6d6912d771ee6391e451dc6f21c5d981fa8075495d62efe1" } } ], "extra": [ 1, 0, 130, 136, 13, 73, 54, 220, 143, 195, 39, 171, 117, 88, 41, 76, 68, 72, 220, 95, 197, 4, 190, 193, 240, 252, 45, 124, 95, 208, 40, 27, 102, 2, 17, 0, 0, 0, 18, 233, 20, 221, 21, 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