Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f02893a757fb8788452723990fabbf407a324145b9fc5804dbf67d8fee9e83e7

Tx prefix hash: ab73a651a1a3dce2ede97a94aa361cceb8f31324103d1d2fccee52a28cfd9f79
Tx public key: 7b5933de945c368130a2a73b16df6a7d05b83f24775fc9d45b6fae54ffb75f92
Timestamp: 1743769666 Timestamp [UCT]: 2025-04-04 12:27:46 Age [y:d:h:m:s]: 00:279:07:23:23
Block: 1254122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197435 RingCT/type: yes/0
Extra: 017b5933de945c368130a2a73b16df6a7d05b83f24775fc9d45b6fae54ffb75f920211000000024060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4461621f9ba9277e3869fd6d8d7151776c90066470e87d8bc937d7c2082b5a92 0.600000000000 1741203 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": 1254132, "vin": [ { "gen": { "height": 1254122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4461621f9ba9277e3869fd6d8d7151776c90066470e87d8bc937d7c2082b5a92" } } ], "extra": [ 1, 123, 89, 51, 222, 148, 92, 54, 129, 48, 162, 167, 59, 22, 223, 106, 125, 5, 184, 63, 36, 119, 95, 201, 212, 91, 111, 174, 84, 255, 183, 95, 146, 2, 17, 0, 0, 0, 2, 64, 96, 246, 210, 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