Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a94b45c11ff1cf885ea445f0e4e1073bb505a9cca1e6a9de61a283e11049f5b8

Tx prefix hash: be6f2ca5e7c66ccae75ae2d8ab39dafe8fa302797af997e9d8a0dc3afb01bb5e
Tx public key: 7dbf7b1433aab1b0d36cc842e5063c8c155378f9758396f97a848c45b8204d5e
Timestamp: 1647222169 Timestamp [UTC]: 2022-03-14 01:42:49 Age [y:d:h:m:s]: 04:250:23:52:55
Block: 457920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1223618 RingCT/type: yes/0
Extra: 017dbf7b1433aab1b0d36cc842e5063c8c155378f9758396f97a848c45b8204d5e0211000000014da16a3a000000000000000000

1 output(s) for total of 0.018653789996 xmr

stealth address amount amount idx tag
00: 05f41bea7a9e3ffc2ce08fbd73068ae3b586fb8a748fe07f4ce0efe4b9019cad 0.018653789996 874307 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": 457930, "vin": [ { "gen": { "height": 457920 } } ], "vout": [ { "amount": 18653789996, "target": { "key": "05f41bea7a9e3ffc2ce08fbd73068ae3b586fb8a748fe07f4ce0efe4b9019cad" } } ], "extra": [ 1, 125, 191, 123, 20, 51, 170, 177, 176, 211, 108, 200, 66, 229, 6, 60, 140, 21, 83, 120, 249, 117, 131, 150, 249, 122, 132, 140, 69, 184, 32, 77, 94, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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: