Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6c500576ce20146509d4409bbaedf345e7e59dc5f4492fc3949d40c4fa85693

Tx prefix hash: 390a458e016763ca24b00c941c348f14fdb96c86478bf4a0c6fcbb85233c9e5e
Tx public key: bd72c28821a6b6261d94298df604ecc430ea52eb4f09f5f300f02121df78b5e7
Timestamp: 1574567481 Timestamp [UTC]: 2019-11-24 03:51:21 Age [y:d:h:m:s]: 06:175:02:13:30
Block: 16141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1518778 RingCT/type: yes/0
Extra: 01bd72c28821a6b6261d94298df604ecc430ea52eb4f09f5f300f02121df78b5e7021100000002d50ca400000000000000000000

1 output(s) for total of 0.542649052494 xmr

stealth address amount amount idx tag
00: cde709df0bdcb3b050725bd5348ce9fb3cf442f38507c1676089ec1e68e725cb 0.542649052494 22355 of 0 -

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": 16151, "vin": [ { "gen": { "height": 16141 } } ], "vout": [ { "amount": 542649052494, "target": { "key": "cde709df0bdcb3b050725bd5348ce9fb3cf442f38507c1676089ec1e68e725cb" } } ], "extra": [ 1, 189, 114, 194, 136, 33, 166, 182, 38, 29, 148, 41, 141, 246, 4, 236, 196, 48, 234, 82, 235, 79, 9, 245, 243, 0, 240, 33, 33, 223, 120, 181, 231, 2, 17, 0, 0, 0, 2, 213, 12, 164, 0, 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: