Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5b14edd5ab2b0829453286bd44a8156aa1924877a1cc6f7e98fb5a4ab0ef993

Tx prefix hash: a8a1552ee45c33b8d6747f20f944cb9e9e601cdae3611d5fcf31c90a0ba0aef3
Tx public key: d9b6a8be2915c7493c6647494ee074d6ea8349ff4c4616cec8076d1722f6f2b1
Timestamp: 1583634850 Timestamp [UTC]: 2020-03-08 02:34:10 Age [y:d:h:m:s]: 06:260:18:47:18
Block: 78394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1605756 RingCT/type: yes/0
Extra: 01d9b6a8be2915c7493c6647494ee074d6ea8349ff4c4616cec8076d1722f6f2b102110000000a27105131000000000000000000

1 output(s) for total of 0.337480689242 xmr

stealth address amount amount idx tag
00: 5bf51000e6e92b923ac9d35b421f92d1cebabf0b2892ae71855e9f918a6912d6 0.337480689242 143838 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": 78404, "vin": [ { "gen": { "height": 78394 } } ], "vout": [ { "amount": 337480689242, "target": { "key": "5bf51000e6e92b923ac9d35b421f92d1cebabf0b2892ae71855e9f918a6912d6" } } ], "extra": [ 1, 217, 182, 168, 190, 41, 21, 199, 73, 60, 102, 71, 73, 78, 224, 116, 214, 234, 131, 73, 255, 76, 70, 22, 206, 200, 7, 109, 23, 34, 246, 242, 177, 2, 17, 0, 0, 0, 10, 39, 16, 81, 49, 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: