Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf282f670eb282cae55f33e7833d46b21b41055c792a04fe09ef22b36a89786a

Tx prefix hash: 67401f9254923acea6fbb2c5d1f659e5310d2de26d76b21da7e3057eb9c634fc
Tx public key: 6c19ad43f6f9619a6f314740e9443926c932be07a8bafd423a345c53b134a331
Timestamp: 1747690642 Timestamp [UTC]: 2025-05-19 21:37:22 Age [y:d:h:m:s]: 01:095:15:08:07
Block: 1286586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332614 RingCT/type: yes/0
Extra: 016c19ad43f6f9619a6f314740e9443926c932be07a8bafd423a345c53b134a3310211000000029f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a54ad3914a1152956e2f8f9485ee4cd7ee8bff9949967f8d43936b10e341e145 0.000600000000 1774053 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": 1286596, "vin": [ { "gen": { "height": 1286586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a54ad3914a1152956e2f8f9485ee4cd7ee8bff9949967f8d43936b10e341e145" } } ], "extra": [ 1, 108, 25, 173, 67, 246, 249, 97, 154, 111, 49, 71, 64, 233, 68, 57, 38, 201, 50, 190, 7, 168, 186, 253, 66, 58, 52, 92, 83, 177, 52, 163, 49, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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: