Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 462d64ed6dbc19446f0898ec1771eb295cf397c44e1093ad0fb2a9f4113080c0

Tx prefix hash: fdec8dfcb3d29e3ad102296e00f28e01ca87e132fb41ea36928bebf09210c376
Tx public key: 483b449d4bd324333921079a0939f4e8f948d06fda149e092b1db542d1ddc70a
Timestamp: 1740239693 Timestamp [UTC]: 2025-02-22 15:54:53 Age [y:d:h:m:s]: 00:357:06:28:55
Block: 1224876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253038 RingCT/type: yes/0
Extra: 01483b449d4bd324333921079a0939f4e8f948d06fda149e092b1db542d1ddc70a0211000000042609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e3407100c709a9b9c22effb5941a4833aa03a0e13daa0862ae7657611c4cb3a9 0.000600000000 1711739 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": 1224886, "vin": [ { "gen": { "height": 1224876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3407100c709a9b9c22effb5941a4833aa03a0e13daa0862ae7657611c4cb3a9" } } ], "extra": [ 1, 72, 59, 68, 157, 75, 211, 36, 51, 57, 33, 7, 154, 9, 57, 244, 232, 249, 72, 208, 111, 218, 20, 158, 9, 43, 29, 181, 66, 209, 221, 199, 10, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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