Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46bd7ca365e3ab00a978875e71d6c056fbff04b7ec208af2a04a5b39dfe3fb4d

Tx prefix hash: 466befd27ba15e11f913a91f84cdcc083a0b8d34a47b6912a50f11024fb3282e
Tx public key: a8f8aba1c179269272dbaffd9b0fc3d5b000b9175b22fdacc0ab19bb30c5a3fa
Timestamp: 1756596956 Timestamp [UTC]: 2025-08-30 23:35:56 Age [y:d:h:m:s]: 01:082:01:27:45
Block: 1358004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325057 RingCT/type: yes/0
Extra: 01a8f8aba1c179269272dbaffd9b0fc3d5b000b9175b22fdacc0ab19bb30c5a3fa021100000001a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f3eac15d2ce3482bcff8e9f5a5ad523289b1f525ed2c7e0cda6288cbc4483dae 0.000600000000 1846013 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": 1358014, "vin": [ { "gen": { "height": 1358004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3eac15d2ce3482bcff8e9f5a5ad523289b1f525ed2c7e0cda6288cbc4483dae" } } ], "extra": [ 1, 168, 248, 171, 161, 193, 121, 38, 146, 114, 219, 175, 253, 155, 15, 195, 213, 176, 0, 185, 23, 91, 34, 253, 172, 192, 171, 25, 187, 48, 197, 163, 250, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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: