Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f9d5f345600fc9332764a8ca5a5d79720d59eeede50cdda7ea418bdef352743

Tx prefix hash: d4f5b2e46aba87ec4664d8ea778d4e52d72c36fd9087be5fb9c393d9d177bd94
Tx public key: a718c0034805421dc07c63a6011cbacad2ad8e4713da60f9d2854b178f1b81ab
Timestamp: 1755104687 Timestamp [UCT]: 2025-08-13 17:04:47 Age [y:d:h:m:s]: 00:048:02:30:25
Block: 1346178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33743 RingCT/type: yes/0
Extra: 01a718c0034805421dc07c63a6011cbacad2ad8e4713da60f9d2854b178f1b81ab021100000014b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18b5ed6929dcd68471d6be52e5c9d359164f99f6470e293dfbfbc1e5c0c6eb9e 0.600000000000 1834075 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": 1346188, "vin": [ { "gen": { "height": 1346178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18b5ed6929dcd68471d6be52e5c9d359164f99f6470e293dfbfbc1e5c0c6eb9e" } } ], "extra": [ 1, 167, 24, 192, 3, 72, 5, 66, 29, 192, 124, 99, 166, 1, 28, 186, 202, 210, 173, 142, 71, 19, 218, 96, 249, 210, 133, 75, 23, 143, 27, 129, 171, 2, 17, 0, 0, 0, 20, 178, 247, 132, 196, 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