Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0c0d1f4ec195b3482700d1461c67dcd6f37aadd1eabb965b1fac962f3aac8ea

Tx prefix hash: cf8addcb1ce1c2721d097ee2470deea79f7f384246da6dcac0e5210181554d56
Tx public key: 841697c95516fd5c3868f202b5d281758b55183b8878bb2d3f8cb8b7fa34da10
Timestamp: 1773512279 Timestamp [UTC]: 2026-03-14 18:17:59 Age [y:d:h:m:s]: 00:247:08:17:23
Block: 1497830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182254 RingCT/type: yes/0
Extra: 01841697c95516fd5c3868f202b5d281758b55183b8878bb2d3f8cb8b7fa34da10021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7dbb9131b7fa818ee58b3080fdfdefa8ecf8eed2944f0ff965c943e06f56f8b9 0.000600000000 1987472 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": 1497840, "vin": [ { "gen": { "height": 1497830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dbb9131b7fa818ee58b3080fdfdefa8ecf8eed2944f0ff965c943e06f56f8b9" } } ], "extra": [ 1, 132, 22, 151, 201, 85, 22, 253, 92, 56, 104, 242, 2, 181, 210, 129, 117, 139, 85, 24, 59, 136, 120, 187, 45, 63, 140, 184, 183, 250, 52, 218, 16, 2, 17, 0, 0, 0, 4, 241, 136, 200, 168, 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: