Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f42206afdd83f725687eddee542ca2a874ebfa5042077f5c1abb1e0602974b9

Tx prefix hash: c469c79573afc987401e8583a5b20158ee31d9ae8f342fcbe9532f4b4bb5abd1
Tx public key: a3b19bc5d1f35107b3497b86ff8e04ac3b1b53808275688e1c4c7ee45c1021f3
Timestamp: 1761794340 Timestamp [UCT]: 2025-10-30 03:19:00 Age [y:d:h:m:s]: 00:011:21:55:53
Block: 1400939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8516 RingCT/type: yes/0
Extra: 01a3b19bc5d1f35107b3497b86ff8e04ac3b1b53808275688e1c4c7ee45c1021f302110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc08083b2caca87a82711fb15adc5d260252b1fd475927f6e4acd84d5b832751 0.600000000000 1889258 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": 1400949, "vin": [ { "gen": { "height": 1400939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc08083b2caca87a82711fb15adc5d260252b1fd475927f6e4acd84d5b832751" } } ], "extra": [ 1, 163, 177, 155, 197, 209, 243, 81, 7, 179, 73, 123, 134, 255, 142, 4, 172, 59, 27, 83, 128, 130, 117, 104, 142, 28, 76, 126, 228, 92, 16, 33, 243, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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