Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 819564ba2b8d03e7edd2b429506df1019bf55fcc035c59de0c6cc2f74073da75

Tx prefix hash: a518d15147189b9da6330b4babc23272c3630f077e819c320f8277a2223b44b0
Tx public key: b764d43ff016ab29d8366debdb7fb254e6486039743b8eaac069e503c6afbca1
Timestamp: 1751092704 Timestamp [UTC]: 2025-06-28 06:38:24 Age [y:d:h:m:s]: 01:141:06:50:59
Block: 1314339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365331 RingCT/type: yes/0
Extra: 01b764d43ff016ab29d8366debdb7fb254e6486039743b8eaac069e503c6afbca1021100000002a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a8f729508e0e28ad9cf0c4df0d5047f841fcde406d38e5ea7189a5cc57c592a7 0.000600000000 1801986 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": 1314349, "vin": [ { "gen": { "height": 1314339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8f729508e0e28ad9cf0c4df0d5047f841fcde406d38e5ea7189a5cc57c592a7" } } ], "extra": [ 1, 183, 100, 212, 63, 240, 22, 171, 41, 216, 54, 109, 235, 219, 127, 178, 84, 230, 72, 96, 57, 116, 59, 142, 170, 192, 105, 229, 3, 198, 175, 188, 161, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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: