Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb08ca785e0f3c7d4e6d862b57504d6871e9add63b3ffc57c082b9de6708372e

Tx prefix hash: 3a53e4947420a4aa728b4b1b20ac8283d907182934d08c9640665d1dd873d802
Tx public key: bd500e0ab4124a9dc92473db41ffd3fbe953cfd6454a38b38800180f20fa698e
Timestamp: 1722018816 Timestamp [UTC]: 2024-07-26 18:33:36 Age [y:d:h:m:s]: 02:116:20:08:09
Block: 1074284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 608477 RingCT/type: yes/0
Extra: 01bd500e0ab4124a9dc92473db41ffd3fbe953cfd6454a38b38800180f20fa698e021100000002e914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 82d98e86b8018a339c0b619cb217cf3d0dcdedefdb8fde09dae4d27111833e99 0.000600000000 1546797 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": 1074294, "vin": [ { "gen": { "height": 1074284 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82d98e86b8018a339c0b619cb217cf3d0dcdedefdb8fde09dae4d27111833e99" } } ], "extra": [ 1, 189, 80, 14, 10, 180, 18, 74, 157, 201, 36, 115, 219, 65, 255, 211, 251, 233, 83, 207, 214, 69, 74, 56, 179, 136, 0, 24, 15, 32, 250, 105, 142, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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: