Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f739717d90786fdb7efae25f27438a36fc72eecd7e8c11c5437d786c68ffd7c7

Tx prefix hash: bb2d866aaa2bd9c8d60cefc599fa1df9cd2c1ca277ab50bc39b82a0f62502236
Tx public key: f08df9fa211e5a8ff831d313a8fc3516b6f2815e6e6256a29f214cfe84f995c7
Timestamp: 1742396614 Timestamp [UTC]: 2025-03-19 15:03:34 Age [y:d:h:m:s]: 01:246:06:41:48
Block: 1242775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440182 RingCT/type: yes/0
Extra: 01f08df9fa211e5a8ff831d313a8fc3516b6f2815e6e6256a29f214cfe84f995c70211000000011db82ba9000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4b0c611b475fdd43394fd2c85c114926baedd0ee02ca2045ced9a8842cc622f7 0.000600000000 1729752 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": 1242785, "vin": [ { "gen": { "height": 1242775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b0c611b475fdd43394fd2c85c114926baedd0ee02ca2045ced9a8842cc622f7" } } ], "extra": [ 1, 240, 141, 249, 250, 33, 30, 90, 143, 248, 49, 211, 19, 168, 252, 53, 22, 182, 242, 129, 94, 110, 98, 86, 162, 159, 33, 76, 254, 132, 249, 149, 199, 2, 17, 0, 0, 0, 1, 29, 184, 43, 169, 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: