Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2aff8641ced9264408f39f4d98ea998cc645ce3dfab09b5c5e221363f2d0cab1

Tx prefix hash: 6891b22a3f4396b647b01a079f40b9eab7b6d791053b4b8da444fd05adf66955
Tx public key: 1ed2ec31ee6f0838428d5803277210767efc770a86c42f5bf35b056211a316cf
Timestamp: 1768156984 Timestamp [UTC]: 2026-01-11 18:43:04 Age [y:d:h:m:s]: 00:034:19:47:25
Block: 1453668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 24725 RingCT/type: yes/0
Extra: 011ed2ec31ee6f0838428d5803277210767efc770a86c42f5bf35b056211a316cf02090000000b8970985800

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7f49f5a3357ce7bcc5308cb0e7c663e253aa775bae0fe9dc2987bbbcbde839b9 0.000600000000 1942738 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": 1453678, "vin": [ { "gen": { "height": 1453668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f49f5a3357ce7bcc5308cb0e7c663e253aa775bae0fe9dc2987bbbcbde839b9" } } ], "extra": [ 1, 30, 210, 236, 49, 238, 111, 8, 56, 66, 141, 88, 3, 39, 114, 16, 118, 126, 252, 119, 10, 134, 196, 47, 91, 243, 91, 5, 98, 17, 163, 22, 207, 2, 9, 0, 0, 0, 11, 137, 112, 152, 88, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369