Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b975c2fb94818a3079c76acded2a29fbe6f20b257b9b60adf00cfcd07d3f20e8

Tx prefix hash: 4f3f6949ab01ae2de1c020bc3894a7c447ecdf0d627c8d9f0119e10a194bf813
Tx public key: 49e100137e39a3bfb213271562bc7219f80596c0b12f2103a1d2c53442f13855
Timestamp: 1759380714 Timestamp [UTC]: 2025-10-02 04:51:54 Age [y:d:h:m:s]: 01:044:10:18:44
Block: 1380912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298063 RingCT/type: yes/0
Extra: 0149e100137e39a3bfb213271562bc7219f80596c0b12f2103a1d2c53442f13855021100000003a5dccd79000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c66ea8e4b3de2f6d014d1aa3da809f7d49ad26e859725708926f336eaf7327d3 0.000600000000 1869023 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": 1380922, "vin": [ { "gen": { "height": 1380912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c66ea8e4b3de2f6d014d1aa3da809f7d49ad26e859725708926f336eaf7327d3" } } ], "extra": [ 1, 73, 225, 0, 19, 126, 57, 163, 191, 178, 19, 39, 21, 98, 188, 114, 25, 248, 5, 150, 192, 177, 47, 33, 3, 161, 210, 197, 52, 66, 241, 56, 85, 2, 17, 0, 0, 0, 3, 165, 220, 205, 121, 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: