Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5518e9bef2b808c52296db2fd74fdb4598ef441551be576e7970f5bb914a795

Tx prefix hash: cf58b39b1f89fe569345835c36080f037af0deff534537f8ff1a02e79ba7fdfb
Tx public key: bc3572b3dd59d19cf692ab71de9c36856e8b546e24cccc129f098b1a2c383eb5
Timestamp: 1742295083 Timestamp [UTC]: 2025-03-18 10:51:23 Age [y:d:h:m:s]: 01:158:19:36:08
Block: 1241933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377823 RingCT/type: yes/0
Extra: 01bc3572b3dd59d19cf692ab71de9c36856e8b546e24cccc129f098b1a2c383eb50211000000091f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f2db2a8126a8278fbea73507c4b8f596ad931e409384a8f0e5d02bf314ffa8e7 0.000600000000 1728906 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": 1241943, "vin": [ { "gen": { "height": 1241933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2db2a8126a8278fbea73507c4b8f596ad931e409384a8f0e5d02bf314ffa8e7" } } ], "extra": [ 1, 188, 53, 114, 179, 221, 89, 209, 156, 246, 146, 171, 113, 222, 156, 54, 133, 110, 139, 84, 110, 36, 204, 204, 18, 159, 9, 139, 26, 44, 56, 62, 181, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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: