Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 353dbd925a0e599b7dcd3f3330874c56740218ce9f1c9780cdff7d92da0edae3

Tx prefix hash: eb4265f6de1f933cf8a2abe0df58bd8b027a9b2ad013428ebbfaa78e6bbdef79
Tx public key: 8c53733b014c25c768703e366ac153dcbd9903560b12d03316265173e11c3b58
Timestamp: 1753863442 Timestamp [UTC]: 2025-07-30 08:17:22 Age [y:d:h:m:s]: 00:201:23:00:57
Block: 1336512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143095 RingCT/type: yes/0
Extra: 018c53733b014c25c768703e366ac153dcbd9903560b12d03316265173e11c3b580211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fec76b80cebea25b8bcc66683a054b5f373328d39c485148d0fc76a3d34287f2 0.000600000000 1824313 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": 1336522, "vin": [ { "gen": { "height": 1336512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fec76b80cebea25b8bcc66683a054b5f373328d39c485148d0fc76a3d34287f2" } } ], "extra": [ 1, 140, 83, 115, 59, 1, 76, 37, 199, 104, 112, 62, 54, 106, 193, 83, 220, 189, 153, 3, 86, 11, 18, 208, 51, 22, 38, 81, 115, 225, 28, 59, 88, 2, 17, 0, 0, 0, 1, 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