Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68d9083d46c6d620935441ca8fcc7c12dc54a850ca967ebaf912a0bdc12b1d68

Tx prefix hash: 0cfb22ae769aea824fe55994165d80878dabfeb0012462b56eb5e2ef40dcfac1
Tx public key: c984840e2c5be569b56164364ef9a4e7d1f4f8fda0c6e4d1a2f60fdaad6d10c4
Timestamp: 1767288974 Timestamp [UTC]: 2026-01-01 17:36:14 Age [y:d:h:m:s]: 00:044:06:11:07
Block: 1446465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 31495 RingCT/type: yes/0
Extra: 01c984840e2c5be569b56164364ef9a4e7d1f4f8fda0c6e4d1a2f60fdaad6d10c4020900000001f3b3285400

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1a4338290bed69fbf58a2b055527c7d9b98c73895f727ca6dffed7909acf6c3d 0.000600000000 1935417 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": 1446475, "vin": [ { "gen": { "height": 1446465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a4338290bed69fbf58a2b055527c7d9b98c73895f727ca6dffed7909acf6c3d" } } ], "extra": [ 1, 201, 132, 132, 14, 44, 91, 229, 105, 181, 97, 100, 54, 78, 249, 164, 231, 209, 244, 248, 253, 160, 198, 228, 209, 162, 246, 15, 218, 173, 109, 16, 196, 2, 9, 0, 0, 0, 1, 243, 179, 40, 84, 0 ], "rct_signatures": { "type": 0 } }


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