Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8141db4e96d9dcab76fa766fc580648bf9fffc13e925c445c6ed1eb576b5893a

Tx prefix hash: a85139d3b5df8705dea93095acc79308ebf269169aa01eff4c1ddbde69b047d6
Tx public key: 0ed01881d5adb1db896fa8a450969fcd88c9cdbd2d2be17578d1c5554c18791d
Timestamp: 1758627940 Timestamp [UTC]: 2025-09-23 11:45:40 Age [y:d:h:m:s]: 01:054:03:41:53
Block: 1374685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305051 RingCT/type: yes/0
Extra: 010ed01881d5adb1db896fa8a450969fcd88c9cdbd2d2be17578d1c5554c18791d02110000000aad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 507de2c1e82405d9d8339e6327047b91a63977c80f60d4d31953eea087cf6b31 0.000600000000 1862770 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": 1374695, "vin": [ { "gen": { "height": 1374685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "507de2c1e82405d9d8339e6327047b91a63977c80f60d4d31953eea087cf6b31" } } ], "extra": [ 1, 14, 208, 24, 129, 213, 173, 177, 219, 137, 111, 168, 164, 80, 150, 159, 205, 136, 201, 205, 189, 45, 43, 225, 117, 120, 209, 197, 85, 76, 24, 121, 29, 2, 17, 0, 0, 0, 10, 173, 121, 72, 208, 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: