Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 505a74993f4c58b57e040a2c828eb92b6cea31630fdbc10d3fc32e28e21c43dc

Tx prefix hash: c56fa8ee9eb9685a2fa0e1ccfb4ad4ab5a4be5506d5452259bc7dd38f7ef0f03
Tx public key: ba74046d27e7f33be46faed85c0976c10a09bc0318920e240ac5224941069e90
Timestamp: 1657058657 Timestamp [UTC]: 2022-07-05 22:04:17 Age [y:d:h:m:s]: 03:242:20:49:55
Block: 537449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 953239 RingCT/type: yes/0
Extra: 01ba74046d27e7f33be46faed85c0976c10a09bc0318920e240ac5224941069e9002110000000533af99f4000000000000000000

1 output(s) for total of 0.010167367185 xmr

stealth address amount amount idx tag
00: 3b44d9e2078174b416cb25956bdc3528b6d4093f4779d949428aada24b7f8edc 0.010167367185 967338 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": 537459, "vin": [ { "gen": { "height": 537449 } } ], "vout": [ { "amount": 10167367185, "target": { "key": "3b44d9e2078174b416cb25956bdc3528b6d4093f4779d949428aada24b7f8edc" } } ], "extra": [ 1, 186, 116, 4, 109, 39, 231, 243, 59, 228, 111, 174, 216, 92, 9, 118, 193, 10, 9, 188, 3, 24, 146, 14, 36, 10, 197, 34, 73, 65, 6, 158, 144, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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) | dinastycoin version: tesla-369