Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7aeb064161ad5b693b325331e678334b3742e61df88a62daa20a2ec0095b355d

Tx prefix hash: 355f2b530979fb543e8c63c45267985f0d82ca688691b0723bd03d61325afcaf
Tx public key: 6392eda157e8bcd4484e59b87cb33473167d6a61eb3ac561e1d356efdfcdc8f4
Timestamp: 1702916613 Timestamp [UTC]: 2023-12-18 16:23:33 Age [y:d:h:m:s]: 02:334:09:38:34
Block: 915928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 764139 RingCT/type: yes/0
Extra: 016392eda157e8bcd4484e59b87cb33473167d6a61eb3ac561e1d356efdfcdc8f4021100000002faf35c9c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 506e9a8d259ab56e06c7e41d17567ceefeb3c8f54fcffe48ed1b3db62cfe84a7 0.000600000000 1373362 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": 915938, "vin": [ { "gen": { "height": 915928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "506e9a8d259ab56e06c7e41d17567ceefeb3c8f54fcffe48ed1b3db62cfe84a7" } } ], "extra": [ 1, 99, 146, 237, 161, 87, 232, 188, 212, 72, 78, 89, 184, 124, 179, 52, 115, 22, 125, 106, 97, 235, 58, 197, 97, 225, 211, 86, 239, 223, 205, 200, 244, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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: