Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85abe258156a7ec2fdd0f648258fcd77ab790c4f07430c548fba026147f5fa7e

Tx prefix hash: 01c4696967c6fff0832e43b5b5fd06ac1973180cffc5c68a4ba2bcb9897a347f
Tx public key: e2eb34ae63be75a701f9c8e2f67c5a37464a3af62576d4f10931c9c337c3756d
Timestamp: 1686513745 Timestamp [UTC]: 2023-06-11 20:02:25 Age [y:d:h:m:s]: 02:336:18:10:56
Block: 780196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 752696 RingCT/type: yes/0
Extra: 01e2eb34ae63be75a701f9c8e2f67c5a37464a3af62576d4f10931c9c337c3756d02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.001595463731 xmr

stealth address amount amount idx tag
00: 0e43b4fd49da4d2874f7c516d8fa5906f1121bb8d4f5b80e01990c91f4b064b6 0.001595463731 1229895 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": 780206, "vin": [ { "gen": { "height": 780196 } } ], "vout": [ { "amount": 1595463731, "target": { "key": "0e43b4fd49da4d2874f7c516d8fa5906f1121bb8d4f5b80e01990c91f4b064b6" } } ], "extra": [ 1, 226, 235, 52, 174, 99, 190, 117, 167, 1, 249, 200, 226, 246, 124, 90, 55, 70, 74, 58, 246, 37, 118, 212, 241, 9, 49, 201, 195, 55, 195, 117, 109, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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: