Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c70efd3d9aa2db6277835295a4e6ee63c8d82e4bb5d492c7fd05e149365e6d4f

Tx prefix hash: 3e5172a28452a38dd2c6995aa1964d992a05d7bbd38c03aa6bd5e603c7ea11fa
Tx public key: e89a9de1b183eea29ff8e154aa0ae73d511cbf1caaf4319d2496f39f65e927b9
Timestamp: 1721095858 Timestamp [UCT]: 2024-07-16 02:10:58 Age [y:d:h:m:s]: 01:113:20:52:41
Block: 1066658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339866 RingCT/type: yes/0
Extra: 01e89a9de1b183eea29ff8e154aa0ae73d511cbf1caaf4319d2496f39f65e927b9021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f260a52b089e5f2fffc617d50a39dc41db1e3237bc723545e70cb5782d53ff9f 0.600000000000 1537325 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": 1066668, "vin": [ { "gen": { "height": 1066658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f260a52b089e5f2fffc617d50a39dc41db1e3237bc723545e70cb5782d53ff9f" } } ], "extra": [ 1, 232, 154, 157, 225, 177, 131, 238, 162, 159, 248, 225, 84, 170, 10, 231, 61, 81, 28, 191, 28, 170, 244, 49, 157, 36, 150, 243, 159, 101, 233, 39, 185, 2, 17, 0, 0, 0, 5, 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