Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0b5b2535dd589a6713feec3959e727513911d641fe07c468f79591d5682e9a8

Tx prefix hash: 7131d6c7e8f68e12a5098984e06d804256e2ef73b97a22981782fec5382731fb
Tx public key: 7e1fdab595a945fe21082a79a01dae5f4dfef9d46a8dac69149e63930d5d6076
Timestamp: 1752612262 Timestamp [UCT]: 2025-07-15 20:44:22 Age [y:d:h:m:s]: 00:123:02:39:07
Block: 1326255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86732 RingCT/type: yes/0
Extra: 017e1fdab595a945fe21082a79a01dae5f4dfef9d46a8dac69149e63930d5d607602110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a6752b1bcdc8d9aa10627c1291f15d4bf0f27dd2399c2b547c95f97d7de65f9 0.600000000000 1814006 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": 1326265, "vin": [ { "gen": { "height": 1326255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a6752b1bcdc8d9aa10627c1291f15d4bf0f27dd2399c2b547c95f97d7de65f9" } } ], "extra": [ 1, 126, 31, 218, 181, 149, 169, 69, 254, 33, 8, 42, 121, 160, 29, 174, 95, 77, 254, 249, 212, 106, 141, 172, 105, 20, 158, 99, 147, 13, 93, 96, 118, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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