Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b742c4dcbc0458d81ee17828ac8e1130a38cd1cd6b9418092a279b84cb4b3bdf

Tx prefix hash: f8ea7c4684602cf3146576ac895d69f936c82331819efa969f26889d5aeb35b6
Tx public key: 8f6218a547746bbbae93ee1f52b75e872020fce0b407d10b532d988a03a71f19
Timestamp: 1748283974 Timestamp [UTC]: 2025-05-26 18:26:14 Age [y:d:h:m:s]: 01:178:23:34:12
Block: 1291508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391986 RingCT/type: yes/0
Extra: 018f6218a547746bbbae93ee1f52b75e872020fce0b407d10b532d988a03a71f190211000000041f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7dcb6d54314383736be408926a9b4f050caa37901b0eecccd524256bbf5f0e1e 0.000600000000 1778979 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": 1291518, "vin": [ { "gen": { "height": 1291508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dcb6d54314383736be408926a9b4f050caa37901b0eecccd524256bbf5f0e1e" } } ], "extra": [ 1, 143, 98, 24, 165, 71, 116, 107, 187, 174, 147, 238, 31, 82, 183, 94, 135, 32, 32, 252, 224, 180, 7, 209, 11, 83, 45, 152, 138, 3, 167, 31, 25, 2, 17, 0, 0, 0, 4, 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: