Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d55b3cad1f4e87da7f23a401398110036004f469e143aae3a9df97513d18914

Tx prefix hash: 0eceb6c0ca45afa85ec1c3fb93e86c01ede2db1bd3c85f818920337eb0e16992
Tx public key: 1eac151017325893c1f336013304385ffe113a4f9cef719ad0410c33cd0acccc
Timestamp: 1740131239 Timestamp [UTC]: 2025-02-21 09:47:19 Age [y:d:h:m:s]: 00:357:20:47:39
Block: 1223985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253455 RingCT/type: yes/0
Extra: 011eac151017325893c1f336013304385ffe113a4f9cef719ad0410c33cd0acccc0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c17c7b2c159af6b7ff15b2a86c2e27138519cb4fb73597ff7e816aa6c57efdda 0.000600000000 1710842 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": 1223995, "vin": [ { "gen": { "height": 1223985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c17c7b2c159af6b7ff15b2a86c2e27138519cb4fb73597ff7e816aa6c57efdda" } } ], "extra": [ 1, 30, 172, 21, 16, 23, 50, 88, 147, 193, 243, 54, 1, 51, 4, 56, 95, 254, 17, 58, 79, 156, 239, 113, 154, 208, 65, 12, 51, 205, 10, 204, 204, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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