Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e0b5cac08f6a4dc6c29f05a1b80141a87ca816ba6f149b5fb75493481cc8cf2

Tx prefix hash: 781d8236653a3fb03ffbeb60742b2d3333788a9dbb8d3c268f0fc198d576974d
Tx public key: 367889b7f7d50c343b0506436da3c16331fce0ef3387e225eae084975825f1aa
Timestamp: 1669852346 Timestamp [UTC]: 2022-11-30 23:52:26 Age [y:d:h:m:s]: 03:170:07:32:24
Block: 642715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 895385 RingCT/type: yes/0
Extra: 01367889b7f7d50c343b0506436da3c16331fce0ef3387e225eae084975825f1aa02110000000383600029000000000000000000

1 output(s) for total of 0.004554266060 xmr

stealth address amount amount idx tag
00: f96b4a096a141941a777cfae62c143de599e8d5a7c083be4ba64a8733ea98d92 0.004554266060 1082618 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": 642725, "vin": [ { "gen": { "height": 642715 } } ], "vout": [ { "amount": 4554266060, "target": { "key": "f96b4a096a141941a777cfae62c143de599e8d5a7c083be4ba64a8733ea98d92" } } ], "extra": [ 1, 54, 120, 137, 183, 247, 213, 12, 52, 59, 5, 6, 67, 109, 163, 193, 99, 49, 252, 224, 239, 51, 135, 226, 37, 234, 224, 132, 151, 88, 37, 241, 170, 2, 17, 0, 0, 0, 3, 131, 96, 0, 41, 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: