Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fd7f5f54c9b57f024ee183a18367f0dad22938fb9e75e364132414f6ce725ab

Tx prefix hash: 553258242d3f3ef796703f1bd8e8cf1ca2feafc1d2821f065ba15943038bb17c
Tx public key: a6bda4de42e3d4cf30da6f7c601500638a3413ab8d253c23727acf94769b5f6d
Timestamp: 1770477647 Timestamp [UTC]: 2026-02-07 15:20:47 Age [y:d:h:m:s]: 00:007:13:02:13
Block: 1472728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 5370 RingCT/type: yes/0
Extra: 01a6bda4de42e3d4cf30da6f7c601500638a3413ab8d253c23727acf94769b5f6d0208e42543e997adc813

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1e259d5998c6cfb6a9d4d16f045e383e95f82746e7afd8c47031b09b162c12e4 0.000600000000 1962010 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": 1472738, "vin": [ { "gen": { "height": 1472728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e259d5998c6cfb6a9d4d16f045e383e95f82746e7afd8c47031b09b162c12e4" } } ], "extra": [ 1, 166, 189, 164, 222, 66, 227, 212, 207, 48, 218, 111, 124, 96, 21, 0, 99, 138, 52, 19, 171, 141, 37, 60, 35, 114, 122, 207, 148, 118, 155, 95, 109, 2, 8, 228, 37, 67, 233, 151, 173, 200, 19 ], "rct_signatures": { "type": 0 } }


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