Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c140dfbf1d210be9eb2577ffeed940e2fd52ddb8a617be183692322b38ea3bd

Tx prefix hash: 394143e137c3b3b6a301c9a629cc0c37bdfd635b174ab0cdcda67f1afcf16b2d
Tx public key: 57367aca5df40fe5a5b7d379aa9e5c454037026b11d4db074f55206d5ee4ac9b
Timestamp: 1772069676 Timestamp [UTC]: 2026-02-26 01:34:36 Age [y:d:h:m:s]: 00:267:19:11:10
Block: 1485917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197010 RingCT/type: yes/0
Extra: 0157367aca5df40fe5a5b7d379aa9e5c454037026b11d4db074f55206d5ee4ac9b021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 36a9920fab00d6d24d0714dd56b5c9a162c62a0a6728a7a89c31846a2ecd0bae 0.000600000000 1975357 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": 1485927, "vin": [ { "gen": { "height": 1485917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36a9920fab00d6d24d0714dd56b5c9a162c62a0a6728a7a89c31846a2ecd0bae" } } ], "extra": [ 1, 87, 54, 122, 202, 93, 244, 15, 229, 165, 183, 211, 121, 170, 158, 92, 69, 64, 55, 2, 107, 17, 212, 219, 7, 79, 85, 32, 109, 94, 228, 172, 155, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: