Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f009dd07be4076f46bc33128b8951487a94b2d78fd6308abb09aef92d197bf81

Tx prefix hash: b39f0692beaeea27ad1f93f6a9ec03e2fa3919be08d8ba85966afcf388b130c1
Tx public key: 6849950a5c78bdb825317e39339e637fef9fa9ee1d9352f1cd79c210e8f62064
Timestamp: 1747299109 Timestamp [UTC]: 2025-05-15 08:51:49 Age [y:d:h:m:s]: 01:189:10:54:49
Block: 1283346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399559 RingCT/type: yes/0
Extra: 016849950a5c78bdb825317e39339e637fef9fa9ee1d9352f1cd79c210e8f620640211000000021f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3d1f30547c263714e6a2b910d6ab7e2ef163f744f7f1fac6b82e1e159a46b036 0.000600000000 1770765 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": 1283356, "vin": [ { "gen": { "height": 1283346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d1f30547c263714e6a2b910d6ab7e2ef163f744f7f1fac6b82e1e159a46b036" } } ], "extra": [ 1, 104, 73, 149, 10, 92, 120, 189, 184, 37, 49, 126, 57, 51, 158, 99, 127, 239, 159, 169, 238, 29, 147, 82, 241, 205, 121, 194, 16, 232, 246, 32, 100, 2, 17, 0, 0, 0, 2, 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: