Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f6f1f5108eebc43fd118ccfc92fcd84746fba5bc37bb17ac2651652707b7b3c

Tx prefix hash: b9a3c3aba7629cdf437eb9b4d3f75b9400734db97c9d72018e99319852bc21cc
Tx public key: 8d3a6c2f58d071f06eeb4ce93471201231bdf2d20511ac9b70924b04508c9537
Timestamp: 1724440360 Timestamp [UTC]: 2024-08-23 19:12:40 Age [y:d:h:m:s]: 02:087:11:43:42
Block: 1094394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 587315 RingCT/type: yes/0
Extra: 018d3a6c2f58d071f06eeb4ce93471201231bdf2d20511ac9b70924b04508c9537021100000001e914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 81d8547b713f2e20e93d9fad00f03a07bffc86679909f236483cb375a5446cc9 0.000600000000 1569511 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": 1094404, "vin": [ { "gen": { "height": 1094394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81d8547b713f2e20e93d9fad00f03a07bffc86679909f236483cb375a5446cc9" } } ], "extra": [ 1, 141, 58, 108, 47, 88, 208, 113, 240, 110, 235, 76, 233, 52, 113, 32, 18, 49, 189, 242, 210, 5, 17, 172, 155, 112, 146, 75, 4, 80, 140, 149, 55, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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: