Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9235855e650703be95ff0e697d4009c6fb2d0bd8d1f26dd3c58987b643e16dc9

Tx prefix hash: 0d2526da0186976287bd6515c19ffb78e13499d5d9ed01b2166bea4ef78a3015
Tx public key: 776f328f637f575987d1ba2fbf34baf35b286a1b87b560f4dbf9985f483fce79
Timestamp: 1576283306 Timestamp [UTC]: 2019-12-14 00:28:26 Age [y:d:h:m:s]: 06:344:05:07:07
Block: 26746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1656452 RingCT/type: yes/0
Extra: 01776f328f637f575987d1ba2fbf34baf35b286a1b87b560f4dbf9985f483fce7902110000001a9159db1e000000000000000000

1 output(s) for total of 0.500472554662 xmr

stealth address amount amount idx tag
00: af135282ed39ee19b588d08662c8f900369458eeeb27d7d873c771d49f94edf0 0.500472554662 44226 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": 26756, "vin": [ { "gen": { "height": 26746 } } ], "vout": [ { "amount": 500472554662, "target": { "key": "af135282ed39ee19b588d08662c8f900369458eeeb27d7d873c771d49f94edf0" } } ], "extra": [ 1, 119, 111, 50, 143, 99, 127, 87, 89, 135, 209, 186, 47, 191, 52, 186, 243, 91, 40, 106, 27, 135, 181, 96, 244, 219, 249, 152, 95, 72, 63, 206, 121, 2, 17, 0, 0, 0, 26, 145, 89, 219, 30, 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: