Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fca296d2c8c634c63c2d0a092ea4f589cd336379f8fca8637d50646968df0c0

Tx prefix hash: 365055e8e105afb547bf8248edd896146c4521eb812652250af8279c389270b6
Tx public key: e5ecbc19b88732ab5376514dc23efa2f7ec185df75a43404f9aef95b7ef0c05b
Timestamp: 1761718292 Timestamp [UTC]: 2025-10-29 06:11:32 Age [y:d:h:m:s]: 01:017:09:45:33
Block: 1400312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278692 RingCT/type: yes/0
Extra: 01e5ecbc19b88732ab5376514dc23efa2f7ec185df75a43404f9aef95b7ef0c05b02110000000125a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 001d7d34336aef30bbe080fe9e8f282409152d8dd4de410911aa4a88a64dcf78 0.000600000000 1888619 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": 1400322, "vin": [ { "gen": { "height": 1400312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "001d7d34336aef30bbe080fe9e8f282409152d8dd4de410911aa4a88a64dcf78" } } ], "extra": [ 1, 229, 236, 188, 25, 184, 135, 50, 171, 83, 118, 81, 77, 194, 62, 250, 47, 126, 193, 133, 223, 117, 164, 52, 4, 249, 174, 249, 91, 126, 240, 192, 91, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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: