Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44b895fcbba8f9b40f3b409337c35446b6cae1d63f5991e842106cebf121efd1

Tx prefix hash: 34e901a3aca3693516f2b1a476ac89397f8a18244e843b2acc885a9074a2ea3a
Tx public key: f01ad95d9e0f07bc7aa70a7bbf8c316489de3c7e254092871cae1eb7d97f4ce6
Timestamp: 1574475289 Timestamp [UTC]: 2019-11-23 02:14:49 Age [y:d:h:m:s]: 06:303:13:35:06
Block: 14945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1624800 RingCT/type: yes/0
Extra: 01f01ad95d9e0f07bc7aa70a7bbf8c316489de3c7e254092871cae1eb7d97f4ce6021100000002f95225a5000000000000000000

1 output(s) for total of 0.547623271343 xmr

stealth address amount amount idx tag
00: 1e91ee62f4ad03881bd13ced0dc0a8edd4c8c79bcdb3c821030c5ac9dea29497 0.547623271343 19562 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": 14955, "vin": [ { "gen": { "height": 14945 } } ], "vout": [ { "amount": 547623271343, "target": { "key": "1e91ee62f4ad03881bd13ced0dc0a8edd4c8c79bcdb3c821030c5ac9dea29497" } } ], "extra": [ 1, 240, 26, 217, 93, 158, 15, 7, 188, 122, 167, 10, 123, 191, 140, 49, 100, 137, 222, 60, 126, 37, 64, 146, 135, 28, 174, 30, 183, 217, 127, 76, 230, 2, 17, 0, 0, 0, 2, 249, 82, 37, 165, 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: