Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d32606a9988d2f4f650b7760f2dbfa9f1da55e15a3c780defb8f3e98502229f7

Tx prefix hash: 7cc6c4ab3979095fde03cf0798c4c81bd2090ba22af96c966410ff391ff533e9
Tx public key: 5e4fa8ee41e3bc9eb67d59bad2a063c7157b6a2cc3363254987abfc3c8968cfa
Timestamp: 1718171912 Timestamp [UTC]: 2024-06-12 05:58:32 Age [y:d:h:m:s]: 02:159:01:28:12
Block: 1042410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 638564 RingCT/type: yes/0
Extra: 015e4fa8ee41e3bc9eb67d59bad2a063c7157b6a2cc3363254987abfc3c8968cfa0211000000010011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cfdc39dbd7c9d1364a192682c0fe8e8841b47cdab33a9063c6b0db4037d99e24 0.000600000000 1511323 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": 1042420, "vin": [ { "gen": { "height": 1042410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfdc39dbd7c9d1364a192682c0fe8e8841b47cdab33a9063c6b0db4037d99e24" } } ], "extra": [ 1, 94, 79, 168, 238, 65, 227, 188, 158, 182, 125, 89, 186, 210, 160, 99, 199, 21, 123, 106, 44, 195, 54, 50, 84, 152, 122, 191, 195, 200, 150, 140, 250, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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: