Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f992f6de7adb4490d3adb7ad5cd898ba7317d9e97d7abff5e1572d237ac8da0

Tx prefix hash: 2a8aa24d50ea8913421335c42228aabde3151518d36a8a596c6d1d58008c8d62
Tx public key: 704fde1624badf283f9bc16da0f1971dbd5f0dc7631119ab1787766962f463db
Timestamp: 1700944561 Timestamp [UCT]: 2023-11-25 20:36:01 Age [y:d:h:m:s]: 01:181:13:16:25
Block: 899572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390964 RingCT/type: yes/0
Extra: 01704fde1624badf283f9bc16da0f1971dbd5f0dc7631119ab1787766962f463db02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.641718438000 dcy

stealth address amount amount idx
00: acf4746f9dc9b7563b322f3cec2dab569884bd5e9846fe0f9b097643a5504e19 0.641718438000 1356031 of 0

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": 899582, "vin": [ { "gen": { "height": 899572 } } ], "vout": [ { "amount": 641718438, "target": { "key": "acf4746f9dc9b7563b322f3cec2dab569884bd5e9846fe0f9b097643a5504e19" } } ], "extra": [ 1, 112, 79, 222, 22, 36, 186, 223, 40, 63, 155, 193, 109, 160, 241, 151, 29, 189, 95, 13, 199, 99, 17, 25, 171, 23, 135, 118, 105, 98, 244, 99, 219, 2, 17, 0, 0, 0, 3, 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