Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 084f9b1e38e238a945801770522dee686b08f52271356724ece9e013018b49ee

Tx prefix hash: 003f02c46bbb8c50eb2809d5cc16b456a8b74a77eabe4f4816eb6627773c4c06
Tx public key: 8718d2eb4b56504bb893e243f96f9926d9000a7db91a26fb217593048396572c
Timestamp: 1758013111 Timestamp [UTC]: 2025-09-16 08:58:31 Age [y:d:h:m:s]: 01:067:05:38:41
Block: 1369597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313897 RingCT/type: yes/0
Extra: 018718d2eb4b56504bb893e243f96f9926d9000a7db91a26fb217593048396572c021100000003b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f2ef3ee2a1e93f96d95f1b4a51c293910de36a0b026e5e5a1780010ed92d014a 0.000600000000 1857672 of 15 -

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": 1369607, "vin": [ { "gen": { "height": 1369597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2ef3ee2a1e93f96d95f1b4a51c293910de36a0b026e5e5a1780010ed92d014a" } } ], "extra": [ 1, 135, 24, 210, 235, 75, 86, 80, 75, 184, 147, 226, 67, 249, 111, 153, 38, 217, 0, 10, 125, 185, 26, 38, 251, 33, 117, 147, 4, 131, 150, 87, 44, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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: