Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fe4f9abcd38009c9de7b45955196a5c6378094166632d735a9b99fcb362c4ec

Tx prefix hash: 3e2e4d10ec2639000a8106d982dc79e19ab1ee7ca9841422fa969f7f770d3f76
Tx public key: 10986b6e66e4ede973aa59d8a857f71d88fda8227d3a9f02c9896cdd0420e1ec
Timestamp: 1716541741 Timestamp [UCT]: 2024-05-24 09:09:01 Age [y:d:h:m:s]: 00:297:03:08:30
Block: 1028895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212370 RingCT/type: yes/0
Extra: 0110986b6e66e4ede973aa59d8a857f71d88fda8227d3a9f02c9896cdd0420e1ec02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5003bc4a8eaaca4ece0a93a5f69e4ef89ca4f1748e081368ffde654bf61486c9 0.600000000000 1496896 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": 1028905, "vin": [ { "gen": { "height": 1028895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5003bc4a8eaaca4ece0a93a5f69e4ef89ca4f1748e081368ffde654bf61486c9" } } ], "extra": [ 1, 16, 152, 107, 110, 102, 228, 237, 233, 115, 170, 89, 216, 168, 87, 247, 29, 136, 253, 168, 34, 125, 58, 159, 2, 201, 137, 108, 221, 4, 32, 225, 236, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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