Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de81c3b9e895b359df928f59aab12afa1d4ddd67d22c34e7b3c170d1f1a7a7f2

Tx prefix hash: 9dcbf33d862bf67e96ad415f71799e5f368d972fb4ae92954448a492994d64ad
Tx public key: e3a58c53bf3175c90edfe379b083396d46d82305b6279a97145e0c798e86d512
Timestamp: 1649331512 Timestamp [UTC]: 2022-04-07 11:38:32 Age [y:d:h:m:s]: 04:039:16:19:38
Block: 475105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1059744 RingCT/type: yes/0
Extra: 01e3a58c53bf3175c90edfe379b083396d46d82305b6279a97145e0c798e86d512021100000001a8c141c5000000000000000000

1 output(s) for total of 0.016359881421 xmr

stealth address amount amount idx tag
00: b19ad226bc424cbad0376dae9eee2b2f4a699af729adf9febd82673dc956664d 0.016359881421 895288 of 0 -

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": 475115, "vin": [ { "gen": { "height": 475105 } } ], "vout": [ { "amount": 16359881421, "target": { "key": "b19ad226bc424cbad0376dae9eee2b2f4a699af729adf9febd82673dc956664d" } } ], "extra": [ 1, 227, 165, 140, 83, 191, 49, 117, 201, 14, 223, 227, 121, 176, 131, 57, 109, 70, 216, 35, 5, 182, 39, 154, 151, 20, 94, 12, 121, 142, 134, 213, 18, 2, 17, 0, 0, 0, 1, 168, 193, 65, 197, 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: