Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e07a546ef11462eeec35e8da742d0ef0ccbff7214fac4b6ac91716b2da9175f

Tx prefix hash: d73c4cf496e182e8b31231e491d7e92a64d9d9d42f2bdc83850d156fd31c9f53
Tx public key: 7c1474f1fc512a0ea65767133ac822b19d61b4b5e93bf205a8c5898861503052
Timestamp: 1648595567 Timestamp [UTC]: 2022-03-29 23:12:47 Age [y:d:h:m:s]: 04:238:11:16:36
Block: 469196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1214298 RingCT/type: yes/0
Extra: 017c1474f1fc512a0ea65767133ac822b19d61b4b5e93bf205a8c5898861503052021100000002c9067537000000000000000000

1 output(s) for total of 0.017114299589 xmr

stealth address amount amount idx tag
00: 00ba225740cd98f7f749c83a004c9824e2eb50d9cee29060c544e5c675343e27 0.017114299589 888090 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": 469206, "vin": [ { "gen": { "height": 469196 } } ], "vout": [ { "amount": 17114299589, "target": { "key": "00ba225740cd98f7f749c83a004c9824e2eb50d9cee29060c544e5c675343e27" } } ], "extra": [ 1, 124, 20, 116, 241, 252, 81, 42, 14, 166, 87, 103, 19, 58, 200, 34, 177, 157, 97, 180, 181, 233, 59, 242, 5, 168, 197, 137, 136, 97, 80, 48, 82, 2, 17, 0, 0, 0, 2, 201, 6, 117, 55, 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: