Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec1f3412995e0abea716524178d96e165566dee302e342dccc0ec5b26d6a8ac7

Tx prefix hash: 0803e3323d7d54121da2ad80655405d8d304a8d35998e6b3bdcab8bffa063ba8
Tx public key: 2e10630a693644f47c8ae1f4575e6507d26b46572cb46b4237065022886041d8
Timestamp: 1770000916 Timestamp [UTC]: 2026-02-02 02:55:16 Age [y:d:h:m:s]: 00:013:05:50:21
Block: 1468754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9459 RingCT/type: yes/0
Extra: 012e10630a693644f47c8ae1f4575e6507d26b46572cb46b4237065022886041d8021100000008e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 63317b2fa7929b9533e8df8700ddb75593071812f995776fa1dc2a80c077291b 0.000600000000 1958002 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": 1468764, "vin": [ { "gen": { "height": 1468754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63317b2fa7929b9533e8df8700ddb75593071812f995776fa1dc2a80c077291b" } } ], "extra": [ 1, 46, 16, 99, 10, 105, 54, 68, 244, 124, 138, 225, 244, 87, 94, 101, 7, 210, 107, 70, 87, 44, 180, 107, 66, 55, 6, 80, 34, 136, 96, 65, 216, 2, 17, 0, 0, 0, 8, 228, 245, 25, 63, 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