Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64a6230ce120d916c910ea3aca3e1026ddd8e30c35bfd1ef97c2a2e7a36239da

Tx prefix hash: de319200dbdfc2808f3fd3ba558adbd9dab7ab7d7458a7e2cd1e11a7f91f9a0b
Tx public key: f587c1d5f66491ea05fcf500292a243fe67c8cab27079f8e2b23874fd06ba9f4
Timestamp: 1703016424 Timestamp [UCT]: 2023-12-19 20:07:04 Age [y:d:h:m:s]: 01:149:17:43:01
Block: 916762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368166 RingCT/type: yes/0
Extra: 01f587c1d5f66491ea05fcf500292a243fe67c8cab27079f8e2b23874fd06ba9f402110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9234660d72891d0785b40d2f30bc3dc4ca615ddc35ca4b54305c5a3fa1d496ae 0.600000000000 1374322 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": 916772, "vin": [ { "gen": { "height": 916762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9234660d72891d0785b40d2f30bc3dc4ca615ddc35ca4b54305c5a3fa1d496ae" } } ], "extra": [ 1, 245, 135, 193, 213, 246, 100, 145, 234, 5, 252, 245, 0, 41, 42, 36, 63, 230, 124, 140, 171, 39, 7, 159, 142, 43, 35, 135, 79, 208, 107, 169, 244, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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