Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f1ced5a5f3ea3e304e52414d574f0a07c68c477ebef42d2bd4911b7160ff4d4

Tx prefix hash: 12fcabd12bdf05ddcff9a24f63f777a1af234aab119f29b8eec12b99fe890911
Tx public key: 54556db5899930baa7bc03dae7a5f96cb1dcb3894750bc9ef8b51040dcd18063
Timestamp: 1756640606 Timestamp [UTC]: 2025-08-31 11:43:26 Age [y:d:h:m:s]: 01:082:16:09:47
Block: 1358337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325157 RingCT/type: yes/0
Extra: 0154556db5899930baa7bc03dae7a5f96cb1dcb3894750bc9ef8b51040dcd18063021100000002ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b3fc231646db396532cfccfb4415cb9e93e8dc93632f626892fc2afd6a6545f5 0.000600000000 1846350 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": 1358347, "vin": [ { "gen": { "height": 1358337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3fc231646db396532cfccfb4415cb9e93e8dc93632f626892fc2afd6a6545f5" } } ], "extra": [ 1, 84, 85, 109, 181, 137, 153, 48, 186, 167, 188, 3, 218, 231, 165, 249, 108, 177, 220, 179, 137, 71, 80, 188, 158, 248, 181, 16, 64, 220, 209, 128, 99, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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: