Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c5f80734610f23f3aeb94fa3b78e0337e7e695d9d633303ba208a2eb4cf22fd

Tx prefix hash: 5c7853f774cf6de776dedff83480add632e374151400331f49eb6575b2ea8829
Tx public key: 071ae5202f053215c8102c26e3429ad7de6c4a492e75e081a5c8e0aeeb7838f2
Timestamp: 1577344413 Timestamp [UTC]: 2019-12-26 07:13:33 Age [y:d:h:m:s]: 06:144:17:50:00
Block: 31965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1504327 RingCT/type: yes/0
Extra: 01071ae5202f053215c8102c26e3429ad7de6c4a492e75e081a5c8e0aeeb7838f202110000000c8a2ee0d9000000000000000000

1 output(s) for total of 0.480936285839 xmr

stealth address amount amount idx tag
00: 98d4f9912b6a49abf5bd370283ed1aa5dc163b54254caf8c9543bcc26327f91a 0.480936285839 53060 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": 31975, "vin": [ { "gen": { "height": 31965 } } ], "vout": [ { "amount": 480936285839, "target": { "key": "98d4f9912b6a49abf5bd370283ed1aa5dc163b54254caf8c9543bcc26327f91a" } } ], "extra": [ 1, 7, 26, 229, 32, 47, 5, 50, 21, 200, 16, 44, 38, 227, 66, 154, 215, 222, 108, 74, 73, 46, 117, 224, 129, 165, 200, 224, 174, 235, 120, 56, 242, 2, 17, 0, 0, 0, 12, 138, 46, 224, 217, 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: