Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b9b644f165f4f89fb47be6958d929967896ace230adc7e9c68dd2e19be3327b

Tx prefix hash: 07769e6cd4c2b597b87b22d1af238d78c8f57eebb8e920c90333cecd45da7fb7
Tx public key: 479cf242bb5840f13cc9a6fbdbbb5bb3a3435ff0801e99058e7c92d8d5f33ef1
Timestamp: 1754246213 Timestamp [UCT]: 2025-08-03 18:36:53 Age [y:d:h:m:s]: 00:114:22:36:55
Block: 1339577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81111 RingCT/type: yes/0
Extra: 01479cf242bb5840f13cc9a6fbdbbb5bb3a3435ff0801e99058e7c92d8d5f33ef1021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89baca74125ddd2414d05bcd54c7cca0f862a3b24077a28e09026c5c093fb0cb 0.600000000000 1827392 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": 1339587, "vin": [ { "gen": { "height": 1339577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89baca74125ddd2414d05bcd54c7cca0f862a3b24077a28e09026c5c093fb0cb" } } ], "extra": [ 1, 71, 156, 242, 66, 187, 88, 64, 241, 60, 201, 166, 251, 219, 187, 91, 179, 163, 67, 95, 240, 128, 30, 153, 5, 142, 124, 146, 216, 213, 243, 62, 241, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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