Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8b7d3156fef7565854c398465e08ed688bc7b61e8b4915739ea3d10e4be7de7

Tx prefix hash: db5f46f794203a4c95178fb750a3f3c66f80a476561ffb4630d7763576a9e088
Tx public key: 6db12ae897058102f606a6eec7329e63c77f5f40dfa511b335cd0c7fc4769784
Timestamp: 1747136688 Timestamp [UTC]: 2025-05-13 11:44:48 Age [y:d:h:m:s]: 01:099:02:33:08
Block: 1282001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335511 RingCT/type: yes/0
Extra: 016db12ae897058102f606a6eec7329e63c77f5f40dfa511b335cd0c7fc47697840211000000011f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9fa3d8ceb0237ee92b6bd38615b045e3f5963c3d6a7af4a9f0a6591afcca57c0 0.000600000000 1769408 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 dinastycoin-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": 1282011, "vin": [ { "gen": { "height": 1282001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fa3d8ceb0237ee92b6bd38615b045e3f5963c3d6a7af4a9f0a6591afcca57c0" } } ], "extra": [ 1, 109, 177, 42, 232, 151, 5, 129, 2, 246, 6, 166, 238, 199, 50, 158, 99, 199, 127, 95, 64, 223, 165, 17, 179, 53, 205, 12, 127, 196, 118, 151, 132, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: