Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b850e978128066abdcb0d130232fc6b8a338c9d1d9f3b2fa9bb96fc0ed38a906

Tx prefix hash: 35739c950819945c4f9b8b5e83261fdee160a79a3e6ef28e1cd3ad1b7ae8b322
Tx public key: 03a57db1347ce1b77aa5c171886a6c4ff4e59fd82468eee697f8a79afe07b850
Timestamp: 1744940770 Timestamp [UCT]: 2025-04-18 01:46:10 Age [y:d:h:m:s]: 00:044:13:58:52
Block: 1263814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31907 RingCT/type: yes/0
Extra: 0103a57db1347ce1b77aa5c171886a6c4ff4e59fd82468eee697f8a79afe07b850021100000004dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a50da7ed23e5a33b1a2eeae188ed303b215206bd38c436dde27a91871560000b 0.600000000000 1751007 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": 1263824, "vin": [ { "gen": { "height": 1263814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a50da7ed23e5a33b1a2eeae188ed303b215206bd38c436dde27a91871560000b" } } ], "extra": [ 1, 3, 165, 125, 177, 52, 124, 225, 183, 122, 165, 193, 113, 136, 106, 108, 79, 244, 229, 159, 216, 36, 104, 238, 230, 151, 248, 167, 154, 254, 7, 184, 80, 2, 17, 0, 0, 0, 4, 219, 181, 113, 193, 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